[opensuse] SuSe updater/zypper cpu-use-prio
Hello everybody, I have a nice piece of hardware equipped with a ahtlon 4000+ cpu. Everytime i boot my computer the suse updater spends several minutes of cputime. No problem, but I can't do anything during this time. Linux has a NICE priority mechanism, to my opinion the suse updater should run on a low priority. Why isn't it designed this way ? Is there a posibilty to do it myself, for instance with the "nice" command. Thanks, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2008-01-07 at 10:50 +0100, Hans defaber wrote:
Hello everybody, I have a nice piece of hardware equipped with a ahtlon 4000+ cpu. Everytime i boot my computer the suse updater spends several minutes of cputime. No problem, but I can't do anything during this time. Linux has a NICE priority mechanism, to my opinion the suse updater should run on a low priority. Why isn't it designed this way ? Is there a posibilty to do it myself, for instance with the "nice" command.
Thanks, Hans Hi Hans,
you are right, opensuseupdater takes a long time to get the list of updates when a lot of repositories are enabled. There are some related feature request for opensuseupdater: - Opensuseupdater shouldn't check for updates every time you login but on defined intervals - Opensuseupdater should wait until system load is low I will do my best to add these features to the next kde version of opensuseupdater. Thomas -------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thomas Goettlicher schreef::
On Mon, 2008-01-07 at 10:50 +0100, Hans defaber wrote:
Hello everybody, I have a nice piece of hardware equipped with a ahtlon 4000+ cpu. Everytime i boot my computer the suse updater spends several minutes of cputime. No problem, but I can't do anything during this time. Linux has a NICE priority mechanism, to my opinion the suse updater should run on a low priority. Why isn't it designed this way ? Is there a posibilty to do it myself, for instance with the "nice" command.
Thanks, Hans Hi Hans,
you are right, opensuseupdater takes a long time to get the list of updates when a lot of repositories are enabled.
There are some related feature request for opensuseupdater: - Opensuseupdater shouldn't check for updates every time you login but on defined intervals - Opensuseupdater should wait until system load is low
I will do my best to add these features to the next kde version of opensuseupdater.
Thomas
-------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
The problem is also Linux. It is difficult to implement priority by the user. So far as I know linux has only 1 default priority and thats 0 for everything. It should have a mechanism to set different default prio's for users, processes and all childs or even for a whole shellprocedure. But linux hasn't it can only set prio for 1 process and after completion you are again on the default prio of 0. Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2008-01-07 at 12:32 +0100, Hans defaber wrote:
Thomas Goettlicher schreef::
On Mon, 2008-01-07 at 10:50 +0100, Hans defaber wrote:
Hello everybody, I have a nice piece of hardware equipped with a ahtlon 4000+ cpu. Everytime i boot my computer the suse updater spends several minutes of cputime. No problem, but I can't do anything during this time. Linux has a NICE priority mechanism, to my opinion the suse updater should run on a low priority. Why isn't it designed this way ? Is there a posibilty to do it myself, for instance with the "nice" command.
Thanks, Hans Hi Hans,
you are right, opensuseupdater takes a long time to get the list of updates when a lot of repositories are enabled.
There are some related feature request for opensuseupdater: - Opensuseupdater shouldn't check for updates every time you login but on defined intervals - Opensuseupdater should wait until system load is low
I will do my best to add these features to the next kde version of opensuseupdater.
Thomas
-------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
The problem is also Linux. It is difficult to implement priority by the user. So far as I know linux has only 1 default priority and thats 0 for everything. It should have a mechanism to set different default prio's for users, processes and all childs or even for a whole shellprocedure. But linux hasn't it can only set prio for 1 process and after completion you are again on the default prio of 0. Hans
If you want to change a user's default nice level you can do this by adding pri=<nicelevel> to the info field in /etc/passwd. Example: tux:x:1000:100:User Tux:/home/tux:/bin/bash => tux:x:1000:100:User Tux,pri=5:/home/tux:/bin/bash As far as I know using the info field isn't very elegant. Perhaps there is a better way. Thomas -------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
There are some related feature request for opensuseupdater: - Opensuseupdater shouldn't check for updates every time you login but on defined intervals - Opensuseupdater should wait until system load is low
I will do my best to add these features to the next kde version of opensuseupdater.
Thomas
-------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
The problem is also Linux. It is difficult to implement priority by the user. So far as I know linux has only 1 default priority and thats 0 for everything. It should have a mechanism to set different default prio's for users, processes and all childs or even for a whole shellprocedure. But linux hasn't it can only set prio for 1 process and after completion you are again on the default prio of 0. Hans
If you want to change a user's default nice level you can do this by adding pri=<nicelevel> to the info field in /etc/passwd. Example: tux:x:1000:100:User Tux:/home/tux:/bin/bash => tux:x:1000:100:User Tux,pri=5:/home/tux:/bin/bash As far as I know using the info field isn't very elegant. Perhaps there is a better way.
You could also always renice to a lower priority, both for CPU and for IO priroties (nice and ionice). And there are more than two levels ;) Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thomas Goettlicher schreef::
On Mon, 2008-01-07 at 12:32 +0100, Hans defaber wrote:
Thomas Goettlicher schreef::
On Mon, 2008-01-07 at 10:50 +0100, Hans defaber wrote:
Hello everybody, I have a nice piece of hardware equipped with a ahtlon 4000+ cpu. Everytime i boot my computer the suse updater spends several minutes of cputime. No problem, but I can't do anything during this time. Linux has a NICE priority mechanism, to my opinion the suse updater should run on a low priority. Why isn't it designed this way ? Is there a posibilty to do it myself, for instance with the "nice" command.
Thanks, Hans Hi Hans,
you are right, opensuseupdater takes a long time to get the list of updates when a lot of repositories are enabled.
There are some related feature request for opensuseupdater: - Opensuseupdater shouldn't check for updates every time you login but on defined intervals - Opensuseupdater should wait until system load is low
I will do my best to add these features to the next kde version of opensuseupdater.
Thomas
-------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
The problem is also Linux. It is difficult to implement priority by the user. So far as I know linux has only 1 default priority and thats 0 for everything. It should have a mechanism to set different default prio's for users, processes and all childs or even for a whole shellprocedure. But linux hasn't it can only set prio for 1 process and after completion you are again on the default prio of 0. Hans
If you want to change a user's default nice level you can do this by adding pri=<nicelevel> to the info field in /etc/passwd. Example: tux:x:1000:100:User Tux:/home/tux:/bin/bash => tux:x:1000:100:User Tux,pri=5:/home/tux:/bin/bash As far as I know using the info field isn't very elegant. Perhaps there is a better way.
Thomas
-------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
I've learned something, I've a lot of fun . I hope that a future release of suse-updater runs on a lower priority. Thanks, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Hans defaber -
Marcus Meissner -
Thomas Goettlicher