this is a question for the folks at RB...
i'm trying to speed up an app that heavily relies on sockets. it
opens a window and performs a bunch of socket stuff... if i profile
the startup section (it never gets to the point of doing any screen
drawing besides the original opening of the window) i find my app
spends %56 of its time in rbframework.dylib HandleEvents().
that makes sense, what's weird to me (from the uniformed outside view
i have) is that 17.3% of that HandleEvents is UpdateMouseCursor, 4.4%
is Window:AboutToYield(), 3.6% in IterateRuntimeWindowList(blahblah)
does this seem normal?? is it something evil i've done to force RB
to think about my UI so much? (is now the right time to confess i use
app.doevents earlier, but not in this section of code)
and an unrelated question for Aaron about the same app profile... i
spend a total of 24% in ml_set_interrupts_enabled... is this all
socket async stuff?
sooo, basically i'm looking for insight into what high level stuff
i'm doing might be calling these lower level things.
thanks,
mike
--
Mike Woodworth
[EMAIL PROTECTED]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
