Had a few n-body cpu wu's and they all lasted only six seconds...

dunx


Task 58688677

Name nbody-Plum_Embedded_4027393_0
Workunit 44893073
Created 1 Jan 2012 | 11:40:03 UTC
Sent 1 Jan 2012 | 11:40:26 UTC
Received 1 Jan 2012 | 11:42:03 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 360356
Report deadline 13 Jan 2012 | 11:40:26 UTC
Run time 6.15
CPU time 8.63
Validate state Valid
Credit 0.77
Application version MilkyWay@Home N-Body Simulation v0.84 (mt)
Stderr output

<core_client_version>7.0.2</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_nbody 0.84 Windows x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 7 max threads on a system with 8 processors
<search_likelihood>-1286.982628237925600</search_likelihood>
11:40:26 (3548): called boinc_finish

</stderr_txt>
]]>

Yup, a week or two ago someone started new task runs that are short & less credits. Also almost a constant shortage of wus due to the validator clogging up.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Just what is the purpose of these very, very short nbody-plum WU's?

As the day has passed I have got more WU's but is this a test of the new server ?

CPU useage of around six seconds is a bit silly...

dunx

Is there a limit as to how many simultaneous n-body tasks one host can run or queue? I see only one task downloaded at a time, run for a few seconds, and then all CPU cores are idle for the rest of that minute, repeat.

I can of course use the CPU for something else, but then the resource share - and ultimately running n-body at all - is a moot point.

---

Is there a limit as to how many simultaneous n-body tasks one host can run or queue?.

There's a limit of 3 tasks / CPU so that's the limit assuming no separation CPU tasks are used.

The number of particles is a bit too small in the current workunits.