Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've got seti@home running in the background and I start it with -nice 19 in the hopes that it doesn't get processor time when I'm doing more important things. However, I've noticed that when I am doing processor intensive work (like compiling or doing some big honking SQL joins) seti still gets about half of the CPU time (according to top).
So my questions are:
1) is this normal?
2) is there a way to really clamp down on seti when a higher priority process comes along?
I'm not interested in seti (I believe that
the best proof for alien intelligence is the
fact that they don't try to conatct us ;})
so I wouldn't know about seti's "niceness" ...
but in general nice is ranged from -20 to 19,
with 0 being the norm.
If you find that your queries run too slow
with seti active, re-nice your sq or the shell
that does the compilingl to -10, -15, -19 ...
1. top is not very accurate w/ cpu activity
2. nice does not chunk up your cpu to portions and divide evenly. That's why sometimes its not the right solution. Instead, it prioritizes cpu time (a bit different).
e.g. Whatever you're doing in the foreground may be waiting for a reply - SETI may not be waiting and hence still use those cycles.
I remember someone released a kernel hack that divides the cpu power in the way you describe it - ie. SETI gets 10% cpu, etc. Maybe try a google search.
nice does not chunk up your cpu to portions and divide evenly
Yeah, I was starting to guess that from watching some SQL queries. What's bugging me is that the same query runs significantly faster if I kill seti first.
I'm going to mess with priorities a bit, but if that doesn't do it I'll probably just dump seti. I've finally got a nice kernel and I really don't want to mess with it. Thanks for the suggestion though.
I don't suppose you have a dual processor? even though seti@home is nice, the compilation would likely only use one so seti would be free to use the other (thus getting about half of the CPU time)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.