[opensuse] Hint: ZMD Eating CPU/Disc
I've built several OpenSuSE 10.x machines, and on all of them, I've had the "fun" of finding that at startup/login, the ZDM stuff just eats CPU & disc. On "quiet" PCs, the CPU fan has to work overtime just to support the stuff, and on laptops, ZMD just eats disc I/O. For a while, I just switched off ZMD. Then I decided to be a bit cleverer. I altered the init script that starts zmd, and changed the start command line to be "/usr/bin/nice -n 19 ${ZMD_BIN} $ZMD_OPTIONS" Viola ! My quiet PC is now quiet, and my laptop now runs well at start up. Yes, ZMD takes a lot longer to sort itself out, but it no longer affects me, and that makes me happy. All I need to do now, is work out why ZMD takes so flipping long to install patches regardless of it's NICEness... (come back YaST, all is forgiven !) GTG -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Onsdag 07 marts 2007 10:44 skrev Gordon Ross:
I've built several OpenSuSE 10.x machines, and on all of them, I've had the "fun" of finding that at startup/login, the ZDM stuff just eats CPU & disc. On "quiet" PCs, the CPU fan has to work overtime just to support the stuff, and on laptops, ZMD just eats disc I/O.
For a while, I just switched off ZMD. Then I decided to be a bit cleverer. I altered the init script that starts zmd, and changed the start command line to be "/usr/bin/nice -n 19 ${ZMD_BIN} $ZMD_OPTIONS"
Viola ! My quiet PC is now quiet, and my laptop now runs well at start up.
Yes, ZMD takes a lot longer to sort itself out, but it no longer affects me, and that makes me happy.
All I need to do now, is work out why ZMD takes so flipping long to install patches regardless of it's NICEness... (come back YaST, all is forgiven !)
GTG
Hi - may we ask as to the whereabouts of bespoken script :-) -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07 March 2007 at 09:54, in message <200703071054.04685.vk@os-academy.dk>, Verner Kjærsgaard
wrote: Onsdag 07 marts 2007 10:44 skrev Gordon Ross: I've built several OpenSuSE 10.x machines, and on all of them, I've had the "fun" of finding that at startup/login, the ZDM stuff just eats CPU & disc. On "quiet" PCs, the CPU fan has to work overtime just to support the stuff, and on laptops, ZMD just eats disc I/O. For a while, I just switched off ZMD. Then I decided to be a bit cleverer. I altered the init script that starts zmd, and changed the start command line to be "/usr/bin/nice -n 19 ${ZMD_BIN} $ZMD_OPTIONS"
Viola ! My quiet PC is now quiet, and my laptop now runs well at start up.
Yes, ZMD takes a lot longer to sort itself out, but it no longer affects me, and that makes me happy.
All I need to do now, is work out why ZMD takes so flipping long to install patches regardless of it's NICEness... (come back YaST, all is forgiven !)
GTG
Hi - may we ask as to the whereabouts of bespoken script :-)
I just edited /etc/init.d/novell-zmd Look for the line that just says "${ZMD_BIN} $ZMD_OPTIONS" and prefix it with "/usr/bin/nice -n 19 " GTG -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-03-07 at 09:54 -0000, Gordon Ross wrote:
Hi - may we ask as to the whereabouts of bespoken script :-)
I just edited /etc/init.d/novell-zmd
Look for the line that just says "${ZMD_BIN} $ZMD_OPTIONS" and prefix it with "/usr/bin/nice -n 19 "
I did the same some days back. What worries me is that those processes run several times a day. I suppose it depends on /etc/zmd/zmd.conf, but it has: refresh-interval=86400 so that should be correct... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF7pmltTMYHG2NR9URArFEAJ9F9HtFIbwc5lX5jMpkjfYJuIbxyACgihDk +rt6Nz6RVdIxSTUEwUT60Kk= =7yER -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
|All I need to do now, is work out why ZMD takes so flipping |long to install patches regardless of it's NICEness... (come |back YaST, all is forgiven !) Mono is the root to all evil. I had the same problem with beagle. 100% cpu load when it indexes. I find it strange because all indexing Should be io-bound. When I do a similar indexing of my disks in perl/sqlite I get 1% cpu load and 100% io-wait, which is more what to expect. All mono programs seem to run at 100% cpu? Poor runtime interrupt handling, poor hardware detection or just bad implementation. Could someone please post some mono benchmarks to kill my suspicion. You can delete zmd, yast/you works fine for me: http://opensuse-community.org/Package_Sources -- MortenB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07 March 2007 at 13:18, in message
, Morten Bjørnsvik wrote:
|All I need to do now, is work out why ZMD takes so flipping |long to install patches regardless of it's NICEness... (come |back YaST, all is forgiven !)
Mono is the root to all evil.
They used to say the same about Java...
I had the same problem with beagle. 100% cpu load when it indexes. I find it strange because all indexing Should be io-bound.
I'd noticed that as well. It really only hits my machines after they've first been built. After that I never notice, so I don't care (Although I might notice now that ZMD is under control) But here's another thought: ZMD & Beagle indexing are background tasks. So why do they either not have code in them to detect & reduce system load, or get fired off at a lower priority. I mean, this is back software engineering/system administration. Hello ?!? Anyone home ? GTG -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Gordon Ross wrote:
All I need to do now, is work out why ZMD takes so flipping long to install patches regardless of it's NICEness... (come back YaST, all is forgiven !)
I got thoroughly sick of this, and finally after having a couple of beers one day I decided to just remove all the zmd-related packages and see what happened. On my next boot, a nice opensuseupdater icon appeared where the zmd-updater one used to be, and my updates work much better now. So, my advice is to ditch zmd. I can't see what the benefit is. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Gordon Ross skrev:
I've built several OpenSuSE 10.x machines, and on all of them, I've had the "fun" of finding that at startup/login, the ZDM stuff just eats CPU & disc. On "quiet" PCs, the CPU fan has to work overtime just to support the stuff, and on laptops, ZMD just eats disc I/O.
For a while, I just switched off ZMD. Then I decided to be a bit cleverer. I altered the init script that starts zmd, and changed the start command line to be "/usr/bin/nice -n 19 ${ZMD_BIN} $ZMD_OPTIONS"
Viola ! My quiet PC is now quiet, and my laptop now runs well at start up.
Yes, ZMD takes a lot longer to sort itself out, but it no longer affects me, and that makes me happy.
All I need to do now, is work out why ZMD takes so flipping long to install patches regardless of it's NICEness... (come back YaST, all is forgiven !)
Correct me if I'm wrong, but of all 10.2 setups I've made, the zmd process always runs at nice level 19 "out of the box". I've checked in on about 50 installations now, and every one runs at 19, no edits made... Anders.
Anders Norrbring
09/03/2007 07:05 >>> For a while, I just switched off ZMD. Then I decided to be a bit cleverer. I altered the init script that starts zmd, and changed the start command line to be "/usr/bin/nice -n 19 ${ZMD_BIN} $ZMD_OPTIONS" Viola ! My quiet PC is now quiet, and my laptop now runs well at start up.
Correct me if I'm wrong, but of all 10.2 setups I've made, the zmd process always runs at nice level 19 "out of the box". I've checked in on about 50 installations now, and every one runs at 19, no edits made...
I'm done this on 10.1 & 10.2 machines, and on both it makes a significant different to startup performance.. GTG -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Gordon Ross skrev:
Anders Norrbring
09/03/2007 07:05 >>> For a while, I just switched off ZMD. Then I decided to be a bit cleverer. I altered the init script that starts zmd, and changed the start command line to be "/usr/bin/nice -n 19 ${ZMD_BIN} $ZMD_OPTIONS" Viola ! My quiet PC is now quiet, and my laptop now runs well at start up. Correct me if I'm wrong, but of all 10.2 setups I've made, the zmd process always runs at nice level 19 "out of the box". I've checked in on about 50 installations now, and every one runs at 19, no edits made... I'm done this on 10.1 & 10.2 machines, and on both it makes a significant different to startup performance..
I just don't understand *why* it should make a difference since zmd runs at 19 anyway? Have you spent any time finding out WHY? -- Anders Norrbring Norrbring Consulting
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-03-09 at 09:54 +0100, Anders Norrbring wrote:
I'm done this on 10.1 & 10.2 machines, and on both it makes a significant different to startup performance..
I just don't understand *why* it should make a difference since zmd runs at 19 anyway? Have you spent any time finding out WHY?
It didn't run at 19 on mine. I did edit it myself to change it to do run at 19, now. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF8T56tTMYHG2NR9URAkvjAJ93toTHzdp7Fu89QOSabEo4xlvWVwCgkpCm mMWlmsXaid1Bt+iXFPODJYs= =hlMe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Anders Norrbring
-
Carlos E. R.
-
David Brodbeck
-
Gordon Ross
-
Morten Bjørnsvik
-
Verner Kjærsgaard