Well I was wondering when I would get a multi task WU well I did today and it grabbed up all four of my CPUs and was done in 2:37 minutes. does this sound right to you? I thought it was great:)

I think I got your speed record beat. longest time for the same thing (4 cores) 1:03.

Well this is interesting: Histogram has 16717 bodies with 16717 in accepted bins
<search_likelihood>-0.234471231698990</search_likelihood>
19:49:16 (292): called boinc_finish

Well I was wondering when I would get a multi task WU well I did today and it grabbed up all four of my CPUs and was done in 2:37 minutes. does this sound right to you? I thought it was great:)

The nbody runs do have varying lengths... are things drastically different than they used to be? (I'm using the same parameter files as the old searches).

---

Well I was wondering when I would get a multi task WU well I did today and it grabbed up all four of my CPUs and was done in 2:37 minutes. does this sound right to you? I thought it was great:)

The nbody runs do have varying lengths... are things drastically different than they used to be? (I'm using the same parameter files as the old searches).

I can't go back far enough in my results to see what the old run times were.
I see my one thread where I said they were gone in a matter of seconds in the old runs and someone commented that was not normal. I think my 4 cores chewed up 40k worth of bodies in just a matter of seconds way back when. Times on this version are between 80-110 seconds for 16k bodies again with 4 cores.

these tasks are whacked in their status.
they show ready to report, no run time remaining, yet when I try to report them they are not ready to be reported and their status changes back to waiting to run.

since I complained it won't give me anymore N bodies. did I insult it or something? LOL roflmao

Hello! You probably aren't receiving new nbody tasks since the nbody workunit generator is currently offline. Also, the run time changes quite a bit based on the input parameters, so it's not unreasonable to have one task take several times longer than another.
For instance, a simulation with 100000 bodies will take much longer to run than one with 16000 bodies, purely due to the additional bodies being simulated.
However, one can have two simulations with the same number of bodies take drastically different amounts of time to complete. For instance, if the size of the simulated stream is X, that simulation will run faster than another simulation with size Y < X and otherwise identical parameters.

Ahhh ok so it isn'5t insulted. LOL and thanks for the info on the bodies:)