Fujimoto Hisa
hisa****@fobj*****
Fri Mar 2 10:35:23 JST 2007
On 2007/03/02, at 10:11, Jacob Wallström wrote: > I agree about your priorities. But is the bridge the problem, the cpu > is 2% even when the app is completely idle. What is crossing the > bridge then? I guess it may be from switching ruby thread freqeutyly using NSTimer. it's for Cocoa GUI control parts. You may see to decrease the cpu usage by putting the following code: require 'osx/cocoa': OSX.ruby_thread_switcher_stop # THIS We may/should imeplement another better way instead of it. For example putting switcher code somewhere (e.g. NSResponder method) using method swizzling. -- hisa > On 2 mar 2007, at 02.06, Laurent Sansonetti wrote: > >> Yes we can do better than that, I have several ideas and even some >> experimental code to reduce the bridge crossing cost (but didn't >> commit it yet because it's not working all the time). >> >> Let's focus on fixing the bugs and making a new release out, then we >> can investigate how to enhance the performance (and also write some >> performance regression tests). >> >> Laurent >> >> On Mar 2, 2007, at 1:14 AM, Jacob Wallström wrote: >> >>> I noticed that the CPU usage hovers around 2% even for a complete >>> empty template application. Is there something that can be done >>> about >>> it? >>> >>> Best regards, >>> Jacob Wallström >>> http://ghostparksoftware.com >>> >>> >>> _______________________________________________ >>> Rubycocoa-devel mailing list >>> Rubyc****@lists***** >>> http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel >> >> _______________________________________________ >> Rubycocoa-devel mailing list >> Rubyc****@lists***** >> http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel > > _______________________________________________ > Rubycocoa-devel mailing list > Rubyc****@lists***** > http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel
