Forum boinc.cz

I think the negative calibration limit for LHC@Home should be adjusted to allow for a larger negative adjustment.
I have a host on it running tx36 and AndyK's PCM is telling me it is claiming about 21 credits per result on average, but is granted only 13.

the client requested work from the backup project for 1 second at a time, twelve times in a row, untill the project ran out of work.
2006-01-21 10:54:48 [---] truXoft add-on: return_results_immediately
2006-01-21 10:54:48 [---] truXoft add-on: cpu_affinity
2006-01-21 10:54:48 [---] truXoft add-on ...

installed tx37 on the dual xeon.
the machine is set to use 3 of the 4 logical processors and has a Connect To setting of 0.05 days
I then set the priority project to no new work and and it proceeded to download work from the backup project.
it downloaded for 1 second of work from Predictor and ...

trux píše:In that case they probably have the unit value estimation set wrongly. Simply do not enable the calibration at that project.

seems like the only option for SIMAP, maybe put a note on the downloadpage?

I gave SIMAP another test run on the dual MP, but it is the same issue again.
realistic claims should be between 5 to 10 credits for the current results, but it is up to 30+ claimed and climbing in less then 10 hours.

2 Mr. Pernod: this problem is unrelated to the core client, it is an error in the app (most likely a noisy WU)
I know the -9 result_overflow is most likely a noise result, I have had these before.
What never happened before is that the next 200+ results that were started directly after the noisy ...

my dedicated SETI host just hosed 200+ results with this error:
<core_client_version>5.3.11.tx31</core_client_version>
<message>There are no child processes to wait for. (0x80) - exit code 128 (0x80)
</message>
directly after it finished this result
<core_client_version>5.3.11.tx31</core_client ...

if you want me to stop testing, just say so, otherwise I will be bugging you with this kind of stuff for a long time

The second machine is bottoming out at about 50% claimed when compared to avergae granted, I'm pulling that one from SIMAP for now as soon as I get home.
The same machines are doing fine on LHC@home, even though that project has wildly varying result-runtimes (from 10 to 25.000 seconds).

I posted ...

trux, I am having a serious problem with SIMAP here
look at this host and its results.
the benchmark values in the host properties matched the values in the client_state.xml last night, but seem to increase with every result returned.

manager 5.2.13, core 5.3.11.tx31

client_state.xml:
<p_ncpus>2 ...

ok, the dual athlon MP went crazy.
In addition to the extreme variations in benchmarks, it also started reporting extreme benchmark values to the SIMAP project
Measured floating point speed 8214.27 million ops/sec
Measured integer speed 5948.17 million ops/sec
I deinstalled BOINC, reinstalled 5.2 ...

I can't reproduce Dorsai's exact issue.
when I suspend network activity, it stays suspended when a project is trying to upload, but when I force an update with the update-button network activity is resumed.
there must be some serious changes in 5.3.11 when compared to the recommended 5.2.13

Dorsai posted a strange thing concerning "suspend network activity" in 5.3.11.tx31 in the thread over on the SETI boards.
Re the network thing, very odd, but Boinc just popped up a message, "16/01/2006 18:43:11||Suspending network activity - user request"...Odd...I turn it off, it turns back on ...

I just looked up some old benchmark scores from the stock 5.2.13 and an optimized 5.3.2, but those were pretty consistent over several runs.
a fluctuation this big will require recalibration every 5 days when the automated benchmarks are run

didn't stop the client, just ran the benchmark a few times.

I just restarted BOINC on the machine, but the benchmarks keep going up and down like crazy.

on the single cpu Athlon XP's it gave around 2GFlops/5.9GIops first time round and remain close to those numbers when rerunning them,
the Xeons ...