<i>I have duplicate Computer IDs after editing my profile - plus work units which are now not being processed.</i>

When I initially connected to CPDN Boinc I set my max CPU preference to 2 and was given the Computer ID 432. Two work units were downloaded and started.

A short while later I decided to limit my CPU usage to 1 (to continue with CPDN classic), and amended my preferences. As there was no immediate effect, I suspended processing.

On resuming Boinc today, errors appear to be generated, followed by a new Computer ID, 595, for the same PC. Two new work units appeared, one of which (032x_000028978) is being processed.

I currently have three BOINC project/climateprediction.net folders:

01ec_000026797
01ed_000026798
032x_000028978

Should I ignore the earlier work units and continue? Should I merge or delete machines?

Thanks

lunecaster

I'm not sure about the WUs, but you should always merge multiple IDs for the same machine. A cleaner database can only run faster. :-)

&gt; I'm not sure about the WUs, but you should always merge multiple IDs for the
&gt; same machine. A cleaner database can only run faster. :-)
&gt;
Yes, a single ID does seem like a good plan really ;-)
I just didn't know if the merge process would sort everything out satisfactorily, including the WU issue. Anyway, Computer IDs now merged successfully, but no apparent change to work unit status so far.

<i>The bigger issue:</i> Why were the multiple IDs generated in the first place? Shouldn't changing the max CPUs preference from 2 to 1 be handled better by Boinc - assuming that's what caused the problem?

lunecaster

<a href="http://www.uk4cp.co.uk/">United Kingdom group</a>

&gt; &gt; I'm not sure about the WUs, but you should always merge multiple IDs for
&gt; the
&gt; &gt; same machine. A cleaner database can only run faster. :-)
&gt; &gt;
&gt; Yes, a single ID does seem like a good plan really ;-)
&gt; I just didn't know if the merge process would sort everything out
&gt; satisfactorily, including the WU issue. Anyway, Computer IDs now merged
&gt; successfully, but no apparent change to work unit status so far.
&gt;
&gt; <i>The bigger issue:</i> Why were the multiple IDs generated in the first
&gt; place? Shouldn't changing the max CPUs preference from 2 to 1 be handled
&gt; better by Boinc - assuming that's what caused the problem?
&gt;
&gt; lunecaster
&gt;
&gt; <a href="http://www.uk4cp/">United Kingdom group</a>
&gt;
Normally it does get handled a bit better, no new host number but it does take until the currently running workunits are finished. It may have been a fluke or there may be a problem with the new CPU scheduler code.
<br>John Keck
BOINCing since 2002/12/08

I did a "2 -&gt; 1" CPU change on a machine here and after updating to get the new prefs, it turned the other one off with the word "Pre-empted" showing up, so it seems to be the proper behaviour (this was the Win 4.02 client)