Number of WU's running on GPU not as configured

wal
wal
Joined: 31 Mar 11
Posts: 5
Credit: 19077368
RAC: 0
Topic 197184

Hello yours,
To understand my question here the configuration of my machine:

Processor: i7-2600 3.4GHz
Memory: 8GByte
GPU: Geforce GTX590
OS: Win7 64bit
GPU-Driver: 314.07 (Multi-GPU Modus deactivated)

I'm running following Projects, that using GPU
- seti@home
- Einstein@home

The other Projects using CPU are
- lhc@home
- cosmology@home
- world community grid

Boinc Preferences:
- On multiprocessor Systems, use at most: 75.00 %
- use at most : 100.00 %

So, that's my configuration.

I have configured, that seti@home and Einstein@home using 0.33 GPU, so i have normally running 6 WU's (0.2+0.33NV(d?)) parallel on my 2 GPU's.

Since yesterday i have only 4 e@h-WU's running parallel on the GPU's. Why?

If i suspend all Projects except einstein@home, boinc start 2 new e@h-WU's, so i have 6 WU's on the GPUs running. If i resume the other Projects, so i have 6 WU's running on the CPU and only 4 WU's running on GPU's. The 2 new started WU's are set to "waiting to run".

Anybody an idea?

Thansk to all
Juergen

AgentB
AgentB
Joined: 17 Mar 12
Posts: 915
Credit: 513211304
RAC: 0

Number of WU's running on GPU not as configured

Hi Juergen

I don´t think i have any answers but another possibly unrelated observation.

I had a look over the tasks you have submitted and noticed a larger than usual number of invalid results.

All invalids i checked appear to be from GPU#1, both BRP4G and BRP5 affected.

May i suggest you post the boinc messages for the boinc-meisters to see.

MarkJ
MarkJ
Joined: 28 Feb 08
Posts: 437
Credit: 139002861
RAC: 0

0.33 x 4 = 1.32 CPUs

0.33 x 4 = 1.32 CPUs required

You've over committed the CPU. BOINC normally will allow over committing (for GPU apps) up to 1 or 1.5 CPUs, depending on the version of the client. If you allow 87.5% processor use it will schedule more tasks at the same time.

ExtraTerrestrial Apes
ExtraTerrestria...
Joined: 10 Nov 04
Posts: 770
Credit: 582278146
RAC: 140134

He's already set it to 75%. A

He's already set it to 75%. A few things I can think of right now:

- are any WUs in high priority mode?
- did SETI change the app, so that your setting no longer applies?
- did you configure Einstein using the website or an app_config.xml? In the latter case a new app may be out which is not yet configured in the file

MrS

Scanning for our furry friends since Jan 2002

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.