Hi, I have the following:

01/12/2008 18:55:08||Starting BOINC client version 6.4.1 for windows_intelx86
01/12/2008 18:55:08||log flags: task, file_xfer, sched_ops
01/12/2008 18:55:08||Libraries: libcurl/7.19.0 OpenSSL/0.9.8i zlib/1.2.3
01/12/2008 18:55:08||Running as a daemon

01/12/2008 18:55:11||Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz [x86 Family 6 Model 15 Stepping 11]
01/12/2008 18:55:11||Processor features: fpu tsc pae nx sse sse2 pni mmx
01/12/2008 18:55:11||OS: Microsoft Windows Vista: Home Premium x86 Editon, Service Pack 1, (06.00.6001.00)


I would like to dedicate one core to running CPDN (or any single project) only, and allow the other core to run various other projects.

Any ideas as to how I do this?

Any help will be much appreciated, thanks in advance.

---

JOIN Team ACC

Set your CPDN resource share to just over 50% - say a numeric value of 501.

Allow CPDN to download one task only, then set No New Tasks.

Keep all you other projects below 50% - say a total numeric value of 500.

Then the CPDN short term debt will steadily, but slowly, increase: it will always be positive, and CPDN will always be the first task to run: with one task only on board, it will occupy one core. The other projects can (and will) fight it out amongst themselves for the remaining core.

You'll need to micro-manage a bit - allow CPDN to download one new task every few months - but that shouldn't be too hard ;-)

Thanks for the quick reply Richard, I'll give it a go. Any problems, I will report it here.

---

JOIN Team ACC

I changed CPDN resource share to 101, and left all my other projects share at 100 (too many projects to bother changing them all); that worked only for a while, so I changed CPDN, only, to 1000, and it works perfectly now; thanks again Richard.

I presume it would be the same technique for PC's with 4 or higher numbers of cores?

---

JOIN Team ACC