Processor use % vs type of work units received |
![]() |
| log in |
Message boards : Number crunching : Processor use % vs type of work units received
| Author | Message |
|---|---|
|
I was wondering if it matter what % I set my processor to use vs what I get for work unit types. I am currently using 4 systems, 3 are set to 50% (all dual core) and 1 is set to 25% (8 cores). | |
| ID: 1277366 · | |
|
In general BOINC will selectively get work for the most capable processor first. | |
| ID: 1277406 · | |
I was wondering if it matter what % I set my processor to use vs what I get for work unit types. I am currently using 4 systems, 3 are set to 50% (all dual core) and 1 is set to 25% (8 cores). The % rule normally doesn't effect GPU tasks. Using 50% is OK, 25% on a dual core probably not. Try TThrottle (see below) If temperature is an issue, just set the CPU and GPU temps. Otherwise you can set a Max Cpu %, like 50%. TThrottle uses a more smooth method. But only works on Windows machines ____________ TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking. | |
| ID: 1277409 · | |
In general BOINC will selectively get work for the most capable processor first. I think you nailed it. The 'nvidia PC' is an older XPS that I upgraded a number of things in, including the processor (Pentium D @3.6), but it is running a EVGA 9600GT card. I know that processor is no match for that card so it is just feeding the hungry card. I just looked and it says the ATI/AMD system at my house received 2 AP unit for the card! Are AP WU's the only ones that can be crunched on the ATI/AMD cards these days? ____________ | |
| ID: 1277598 · | |
|
An Nvidia card presents a very low demand on the CPU. Basically so long as the motherboard will take the card and the operating system the drivers then the the card will work - I think the CPU just acts as an interface between the RAM/HD and the GPU (someone will be along soon to put me right on this...) | |
| ID: 1277608 · | |
A higher end NVIDIA card will use up to 15% of one virtual core, continuesly. So they too need to reserve a CPU core. This is needed because the "feeding" can take up the entire CPU core for even a couple of seconds And the work done by the GPU outweighs the CPU work by far. So you want to keep the GPU going. ____________ TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking. | |
| ID: 1277638 · | |
|
Thanks Fred. | |
| ID: 1277640 · | |
|
Multibeam ATI apps only use a CPU a lot at the startup of a new work unit, under a minute, and then essentially nothing (< 3%) until it's done. Don't have any experience with Astropulse apps. | |
| ID: 1277737 · | |
|
the FX CPU's are a bit fussy about giving the GPU time while MB WU's are running. Mike has discovered that allowing the GPU to have 1 or 2 CPU cores massively increases the ATI/AMD Radeon GPU productivity | |
| ID: 1277757 · | |
|
Wow, this is going well now! | |
| ID: 1277890 · | |
|
Well back of the envelope calculations says your rig is doing MB 6.03 roughly at 45-55 credits per hour per core (ignoring the overflows). So once your pending settles down you should be getting around 2400 credits per day just from MB tasks with two cores. Get all eight cores going and it would place it over 9000 (insert DragonBall Z joke here). Of course I don't know how much CPU time is loss for an ATI/AMD AP app and what the credits/hour it generates on average. | |
| ID: 1277993 · | |
|
IMHO both ATI and NVidia GPUs need CPU time, both high-end GPUs need about | |
| ID: 1278169 · | |
IMHO both ATI and NVidia GPUs need CPU time, both high-end GPUs need about Not all Nvidia GPUs have a problem with VLARs. | |
| ID: 1278385 · | |
|
As far as i can tell since the latest fix vlar do not go to any type gpu | |
| ID: 1278440 · | |
As far as i can tell since the latest fix vlar do not go to any type gpu Well said. Some of us are not afraid of the vlar boogeymen. ]:) | |
| ID: 1278447 · | |
Message boards : Number crunching : Processor use % vs type of work units received
| Copyright © 2013 University of California |