Hehe, that reminds me time when i had clients using a st-80 app on a server workstation. At that time, MVC UI was still polling, with some kind of heart beat for relaxing CPU cycles... But RAM was not cheap and was the true bottleneck, our app already did already consume a few Mbytes. Naturally users did notice that they would not be swapped out of memory if they shake the mouse. So they more or less instinctively shake the mouse and we got lot of complaints from system engineers. They could not understand how a modern application could waste so many cycles for nothing and be such a bad citizen... I see that many years later, despite our (late) conversion to event driven UI, we still have some remnant ghosts...
Nicolas 2012/6/4 Sven Van Caekenberghe <[email protected]>: > Yes, we should at least understand why this happens. > > BTW, another related question is: when running headless, do we actually need > those 6 processes ? > > Sven > > On 04 Jun 2012, at 21:56, Igor Stasenko wrote: > >> i just wonder, what takes so much CPU time, even if it completely idle... >> >> >> 4831- NBCog 4.8 >> 51519- NBCog 3.5 >> >> if i kill a UI process, the load goes down to 2.5-3 % ... >> still too much. >> >> i would like to know how we can minimize this. >> The reason why i concerned is straightly pragmatic: extending battery life.. >> >> i found that if i run completely on battery.. it depleting quite fast >> with VM running (and i don't do anything just coding, i.e not running >> benchmarks, but more thinking and typing). >> >> -- >> Best regards, >> Igor Stasenko. >> > >
