On 5/23/07, Mehmet D. AKIN <[EMAIL PROTECTED]> wrote:
We have a java spell checking daemon which is started at boot time. Here is the results for a sample system in idle state: 23.0% hald-addon-cpuf : queue_delayed_work_on (delayed_work_timer_fn) 15.9% java : schedule_timeout (process_timeout) 10.4% knotify : schedule_timeout (process_timeout) 9.8% beagled : schedule_timeout (process_timeout) 9.6% <interrupt> : libata 5.1% <interrupt> : ipw2200 Question is, aferemonetioned java daemon practically does nothing but waits for connections, why does it wakeups so much? I dont think GC threads wake-up so frequently or do they?. Can anyone else confirm this? (Write a simple java app which only sleeps and check its powertop output) It would be nice to identify this probem. There are many java applications, which might benefit from this.
On my system, a Java6 1.6 app that just does Thread.sleep() runs about 19 interrupts a second (get powertop 1.3 for the number of times). Same with a blocking System.in.read(). Apparently it keeps calling gettimeofday. FYI there's a patch that may be able to reduce knotify usage on the powertop tips&tricks page. - Jason
_______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
