On Jan 6, 2007, at 1:26 PM, Stefan wrote:
We probably discussed this issue in the past, but..
More or less idle RB apps get roughly 30-60% of CPU time (according
to OS X'
activity monitor), Cocoa apps's don't.
Thus, I wonder is RB apps do busy waiting for the next event to
appear. And for
Mach-O build, additionally, I wonder why they don't go fully idle
until the next appears
appears.
We only poll certain things, the most prevalent being sockets. If you
have a listening or connected socket, we will poll them roughly every
5 ticks.
However, I've never seen a truly idle app use more than 1.5-3.0%. To
test this, build an empty project, and launch it from the finder. Look
at the processor usage. For me, it's 0%.
So the question is, what does your app have that the default app
doesn't? Do you have threads that are running in the background? Do
you have lots of socket communications? Timers? Constant redraws?
-Jon
--
Jonathan Johnson
[EMAIL PROTECTED]
REAL Software, Inc.
_______________________________________________
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>
