Carsten Haitzler (The Rasterman) wrote: <snip> > xdaliclock!!! no wonder! e has to recalculate the dropshadow shapes > all the time - i mean i spent a lot of time optimsing that heavily, > but... doing realtime gaussian blurrs takes a bit of grunt.
Yeah, but it's reall pretty! It does a very good job of it. It's very smooth. >> With or without it (xdaliclock), I don't see much impact though. > > > well thats mostly the kernel - e will use cpu when it needs it - as > much as it can get - then go back to idling waiting for something it > needs to do. your kernel will handle 5giving up the cpu to e and > takign it away as needed. e doesnt run threads or fork 1000's of > processes so its only 1 slot in your kernel's process table and thus > should have minimal impact in general - even if eating 100% cpu. It's sweet. I would have suspected that I would have seen some degradation because of the xdaliclock app, but if you think about, it's still got 80% of the cpu to play with. :) -- Until later, Geoffrey ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
