On Sat, 25 Feb 2012 18:33:09 +0000 Mick <michaelkintz...@gmail.com> said:
> On Friday 24 Feb 2012 10:28:22 you wrote: > > On Fri, 24 Feb 2012 09:05:25 +0000 Mick <michaelkintz...@gmail.com> said: > > > On Friday 24 Feb 2012 01:05:15 Carsten Haitzler wrote: > > > > On Fri, 24 Feb 2012 00:57:58 +0000 Mick <michaelkintz...@gmail.com> > said: > > > > > On Friday 24 Feb 2012 00:21:00 Carsten Haitzler wrote: > > > > > > you just need xproto + xlibs. > > > > > > > > > > > > just remember that compositing will be broken for you due to your > > > > > > server being old anyway, but e/efl will compile and run but > > > > > > compositing may fail (and we will be moving to compositing only in > > > > > > future). > > > > > > > > > > Oops! Won't we have an option to switch it off if we want to? > > > > > > > > in future - no. for e17 release it'll stay a module, but after that > > > > it'll be compositing only. get used to it - i suggest u use it and > > > > report bugs/issues. :) > > > > > > Well, I can't say it is bug(s) but it is a matter of overall > > > responsiveness and resources used, especially on older systems. > > > Composite uses (slightly) more CPU and memory on my amd64 box and more > > > so on an old x86 with a PIII on it. > > > > the lowest-end machine i've use it on is a pentium-m@600mhz - it works very > > well there. sure - not silky smooth but very usable... considering its > > copying mountains of data around and rendering everything with the cpu > > (clients included) it's pretty amazing. :) seriously... software > > compositing is working (decently) on PHONES... yes - its a price to pay - > > software compositing adds an extra copy from x to local data first before > > drawing and then writing it back to x - so it adds extra overhead. theres > > no zero copy path like gl + texture-from-pixmap. > > > > > Plus when say I watch something in mplayer and I move focus to another > > > window, then the mplayer window becomes transparent and the picture > > > fades. Since the cursor does not automatically follow my eyes I just > > > switch composite off. > > > > you can select what style u want with compositing - its there in the comp > > gui to select. you can have the fading disabled - wobbles too etc. > > Hmmm ... my PIII comes up with this compositor warning: > > "Your screen does not support OpenGL. Falling back to software engine" > > It seems it doesn't like the Radeon Mobility M6 LY that this old laptop is > running. I don't recall having this problem before. I should try a later > snapshot to see if it persists. evas is the compositing engine. evas needs a gpu (and opengl implementation) that supports GLSL shaders. that means opengl-es2 level stuff (most modern arm soc's with gpu's do this - so even on your phone and tablet), and for desktop it means something like a geforce 6xxx or newer - don't know about ati cards. for intel - not sure, but the gma3150 and 945gm definitely do shaders (tho 3150 has the problem that it has pixel shaders only in hardware - it does vertex in software and that hurts a lot for text and complex clipping geometries). > I can see in top enlightenment runs between 3.4 - 5% of the CPU with bursts > up to 35.9 - 54% when I move between windows (a couple of aterms and a xterm). yup. expect it to consume as much cpu as it can get its hands on to keep up with the workload. the more it has to update/re-render, the more it will have to use (the more pixels and the more frames). > Without composite enlightenment shows between 0.5 - 2.5% of the CPU with > bursts up to 7.9% when I move between windows. > > So, yes it is usable, but if I am doing something heavy on this little box > like compiling, compressing files, etc, then it slows down noticeably and > this is why I would rather give up compositing effects for functionality. not going to happen for E. having a non-compositing path is unsustainable if we want to move ahead and implement new and interesting things. to sustain such a path means holding us back in a half-arsed hobbled world. if you are compiling, compressing and doing heavy work on a p3... in this day and age, i'd be amazing it still managed to boot. :) seriously - with x, and software compositing, we pay about a 100% overhead for software compositing compared to opengl (when it comes to pixel paths). there is nothing we can do about that without some x extensions OR by going down to dri/drm and then we have to build a special solution per driver as the drm lib apis vary, AND then it means also driver changes to allow for swapping, not copies). technically if we were a wayland compositor we could get rid of that overhead :) i put up a video of software comp: http://youtu.be/ESwhnWM1cKw old sony vaio x505 laptop, pentium-m @ 600mhz, 1024x768 screen, software compositing. > Are there some settings in the composite configuration, which will minimise > the load? disable smooth scaling. use a style with no translucency (default fades windows out and wobbles them on focus change - use the still style instead of default for example). also last week i fixed an overdraw problem in evas where its clip-outs had it drawing much more than it should (though you dont notice except with performance) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
