View Single Post
Old 07-19-2013, 09:47 AM   #5
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
As for the RAM/CPU usage, Java has a pretty specific memory handling, and, IIRC, on the PW, it sits nicely between 60 and 70MB, which is roughly 30% of the 250MB of RAM available, so that also looks okay.

And, by default, ps reports the average total CPU usage over the complete lifetime of a process (ie. it's not a snapshot on the cpu usage at the exact moment you ran ps), so, depending on how early after boot/framework boot you launch ps, since the framework pretty much sits at 100% CPU during boot, that might not be completely extraordinary either.

That said, the most common reason for the framework *really* looping at 100% cpu is an indexing loop. Check the logs to see if it's looping on a book (beside the usual compacting/cleanup tasks).

Last edited by NiLuJe; 07-19-2013 at 06:34 PM.
NiLuJe is offline   Reply With Quote