tag:blogger.com,1999:blog-4535528758590979933.post1531431923585899409..comments2022-03-11T02:58:06.682-05:00Comments on Casually Defiant: Compiz and FedoraKristian Høgsberghttp://www.blogger.com/profile/01071042513787555957noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4535528758590979933.post-49340820295355534402007-12-06T19:00:00.000-05:002007-12-06T19:00:00.000-05:00Hi there, Looks like you may have gotten glxcompmg...Hi there,<BR/> Looks like you may have gotten glxcompmgr in fc6? I was searching re compiz and e17 and thought you may be able to help.. <BR/><BR/>Where can I get an fc6 or 7,8 etc rpm that has glxcompmgr? Have you tried to get it going with e17 yet?<BR/><BR/>Feel free to email meauziemanhttps://www.blogger.com/profile/15588367540271882215noreply@blogger.comtag:blogger.com,1999:blog-4535528758590979933.post-70358553760091532552007-09-07T04:58:00.000-04:002007-09-07T04:58:00.000-04:00More statistics but this time gleaned from powerto...More statistics but this time gleaned from powertop. System tested is as before. Headings generally apply to all subsequent tests unless another heading says otherwise.<BR/><BR/>All wake up hog programs killed<BR/>-------------------------------<BR/>Laptop mode on<BR/>--------------<BR/>Backlight off<BR/>-------------<BR/>Powersave max<BR/>16.5 wakeups per second, 11W<BR/>Powersave ondemand<BR/>21.7 wakeups per second, 10.9W<BR/>Backlight on, 100%<BR/>------------------<BR/>Powersave ondemand<BR/>------------------<BR/>20.8 wakeups per second, 13.0W<BR/>Bluetooth and wifi on (via soft killswitch)<BR/>175.6 wakeups per second, 15.4W<BR/>Bluetooth and wifi on, compiz on<BR/>240.5 wakeups per second, 15.4W<BR/>Bluetooth and wifi off, compiz on<BR/>94.0 wakeups per second, 13.1W<BR/>Bluetooth and wifi off, compiz off (once AIGLX is turned on your interrupts will rise until Xorg is restarted)<BR/>80.2 wakeups per second, 13.0W<BR/>(reboot, default programs running)<BR/>Brightness 100%, metacity, wifi on, bluetooth on<BR/>231.1 wakeups 15.5W<BR/>Hardware killswitch<BR/>69.9 wakeups 13.2W<BR/>killall thinkpad-keys<BR/>51.7 wakeups 13.0W, 55.4 wakeups 13.1W<BR/>kill hald-addon-storage<BR/>21.4 wakeups 13.0W<BR/>(could try killing mixer_applet2 but it doesn't seem worth it)<BR/>101.4 wakesups 13.1W<BR/>(blinking cursor in vi seems to use up 0.1W)<BR/>(reboot) hardware killswitch, killall thinkpad-keys, kill hald-addon-storage, disabled laptop-mode<BR/>19.0 wakeups 13.4WAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4535528758590979933.post-3993548976956600902007-08-25T13:46:00.000-04:002007-08-25T13:46:00.000-04:00I sat down and use a Gutsy beta to do some power t...I sat down and use a Gutsy beta to do some power testing last week. I have a small "Energy Monitor" adapter from Maplins (a gadget inspired by the world famous Dave Jones) and I used that to try and monitor power consumption through the mains by booting the machine without a battery installed. All testing was done with Ubuntu Tribe 4 on a Thinkpad T60 (graphics card is an Intel 940). I will put the wattage the monitor measured on the left and the action being done on the right. The monitor isn't perfect but I'd guess it's accurate to within 2W.<BR/><BR/>4W - Laptop was off.<BR/><BR/>Ubuntu Feisty fresh install<BR/>25-26W - Laptop was idling at Grub boot menu.<BR/>27W - Laptop doing fsck during boot.<BR/>24W - Idling in X at GDM.<BR/>(metacity is the window manager)<BR/>23-24W - Idling in X at GNOME backdrop.<BR/>19W - Idling in X at GNOME backdrop with brightness set to 0.<BR/>15-16W - Idling in X at GNOME backdrop with lid shut.<BR/>30W - Within X and glxgears is running brightness set to 0.<BR/>39W - cat /dev/shm/words in X within a GNOME terminal.<BR/>(compiz is the window manager)<BR/>19-20W - Idling in X at GNOME backdrop with brightness set to 0.<BR/>30W - Within X and glxgears is running.<BR/>(disable DRI in xorg.conf, metacity as window manager)<BR/>19-20W - Idling in X at GNOME backdrop with brightness set to 0.<BR/><BR/>18-19W - Idling at a virtual terminal, cursor blinking disabled with cron/anacron turned off.<BR/>20W - Idling at virtual terminal, cursor blinking disabled after using telinit 1 to go to single user mode (strange - perhaps powersaved being disabled didn't help?)<BR/><BR/>Gutsy Tribe 4 fresh install<BR/>(45W peak during installation)<BR/>24-25W - Idling in X at GDM.<BR/>(compiz is the window manager)<BR/>24-25W - Idling in X at GNOME backdrop.<BR/>19-20W - Idling in X at GNOME backdrop with brightness set to 0.<BR/>16-17W - Idling in X at GNOME backdrop with lid closed.<BR/>39-40W - cat /dev/shm/words in X within a GNOME terminal, brightness 0.<BR/>31W - Within X and glxgears is running.<BR/>(metacity is the window manager)<BR/>19-20W - Idling in X at GNOME backdrop with brightness set to 0.<BR/>31W - Within X and glxgears is running.<BR/>(disable DRI in xorg.conf, metacity as window manager)<BR/>19-20W - Idling in X at GNOME backdrop with brightness set to 0.<BR/><BR/>20W-21W - Idling at virtual terminal, cursor blinking disabled after using telinit 1 to go to single user mode.<BR/><BR/>After putting the battery back in and unplugging the mains I used powertop of Gutsy to get some more results. powertop estimated that the energy draw was 10.8W with metacity and when DRI was on, 10.8W with compiz and when DRI was on and 10.6W with metacity and when DRI was off.<BR/><BR/>(it is very hard to post results using this very small comments box)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4535528758590979933.post-49860897204305220522007-08-19T17:40:00.000-04:002007-08-19T17:40:00.000-04:00I think giving "support normal 2d-rendering" will ...I think giving "support normal 2d-rendering" will be useless, compiz base some parts of code from metacity, it support metacity themes, it got powerful keyboard shortcuts management, but this is compositing manager, it gives a lot more that metacity in user experience, and functionality. If there is some group of users that feel there is functionality in metacity that they can't live without and they want to use compiz then compiz should provide it, in form of plugin "metacity" for compiz with that functionality(for example). You dont need to write that plugin, just write request for that plugin and specs what that plugin should provide, compiz community will bring it. I thnik plugin that will provide functionality compatybility of "kwin,metacity" for compiz is greate idea.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4535528758590979933.post-23600368367357573352007-08-17T10:54:00.000-04:002007-08-17T10:54:00.000-04:00On "Once we get there, the default compositor will...On "Once we get there, the default compositor will be compiz." and "We're not working on making metacity a compositing manager.": That afaics and iow means: some people (those with composing-capable hardware and drivers) will run compiz, the other stick to metacity. That's not a problem per se, but the two often feel and react differently -- that's utterly confusing for the users, as a action on the same distribution might result in a different behavior on different machines.<BR/><BR/>I'm wondering if it would make sense to support normal 2d-rendering (not sure if that's the proper tem, but I suppose you'll know what I mean) in compiz, so everyone can use the same window manager and everything feels and acts similarly.Thorsten Leemhuishttps://www.blogger.com/profile/12285919704852601523noreply@blogger.comtag:blogger.com,1999:blog-4535528758590979933.post-74014879014117398342007-08-16T14:49:00.000-04:002007-08-16T14:49:00.000-04:00Good post, thanks for the update Kristian!Good post, thanks for the update Kristian!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4535528758590979933.post-38422806314635838422007-08-16T14:22:00.000-04:002007-08-16T14:22:00.000-04:00When idling, compiz and metacity use exactly the s...<I>When idling, compiz and metacity use exactly the same amount of power. There are no code paths anywhere in the stack that "turn on 3d powerplanes". My bet is that it's more power consuming to wake up all applications to redraw their exposed areas under the window you're dragging than it is for compiz to just recomposite that out of textures already in video memory.</I><BR/><BR/>This is not quite the way I see things currently.<BR/><BR/>First, about the "3d powerplanes". Some drivers (for example the nvidia binary driver) will clock the card higher when in 3D mode, which results in faster battery drain. More generally, OpenGL implementations are tuned for performance and not for power efficiency, and make heavy use of busy waits for example.<BR/><BR/>Second, about waking up applications. Although your point is true, re-compositing a screen from a number of pixmaps laying in VRAM is not exclusive to 3D compositing managers like compiz, but can be achieved via a 2D compositing manager as well. So this is not an advantage of 3D compositing managers either.<BR/><BR/>Real world power usage benchmarks would surely be very interesting, but I'm quite confident what the results look like today.<BR/><BR/>Now what if one wants to solve that power & heat issue. Today, the driver has no way to know if the full power is needed (for that doom 5 game) or not (doing word processing). Maybe the application should tell what it wants, but no mechanism for that currently exists.Anonymousnoreply@blogger.com