Message boards : BOINC client : Workload problem on SMP system
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 Oct 07 Posts: 2 |
Hi, I'm running a WCG project units for several months on a server with single dual-core processor. The operating system is Oracle Enterprise Linux. The server is mostly idle but there are some periods of heavy workload. First I had a problem running two work units simultaneously, which has been solved by setting the "cpu_usage_limit" parameter to 200. But it seems like if the work unit finishes it's work during the heavy workload period the client does not start another work unit and the system may be running only one work unit for days. The only workaround I found is to restart the client. Currently I'm running client version 5.10.22, but this behavior has been observed on all previous versions I've used. I always compiled client myself from sources. Has anyone seen this problem before and is there any workaround other than writing a script to monitor workload and restart client when necessary? Vadim. |
Send message Joined: 19 Jan 07 Posts: 1179 ![]() |
First I had a problem running two work units simultaneously, which has been solved by setting the "cpu_usage_limit" parameter to 200. That parameter's maximum is 100. I don't know if there is proper checking, or undefined behavior happens if it's set outside its range. |
Send message Joined: 15 Oct 07 Posts: 2 |
Yes, you are right. I've just set that parameter to 100 and the client is still running two processes. Probably that was the same issue and it was temporary resolved after I changed the value of that parameter, so it made me think that that change helped. Anyway my problem is the following: most of the time I see two processes in "top", both consuming 100% CPU. Sometimes I can see only one process consuming 100% CPU and if this happened only restart of the client can change things back to seeing 2 processes in "top". Vadim. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.