I am also "unhappy" about this change. I have dedicated all of my Ubuntu machineds to CEP2. I7 950 (8), I7 920 (8), 2 1090t (12), and an Amd X4 955 (4). A total of 32 CPUs on 5 hosts. I have donated 5 years and 296 days to this project as these 5 machines run 24x7 and I have never noticed a problem. Now with this change, I will only be able to run 5 tasks instead of 32, that does not make sense. This will significantly impact my ability to contribute to this project. Since I have donated over 20 years to all of the other active projects, with the exception of CWP, and DDDT2 , and I cant get any DDDT2, it looks like all of my contribution will go to CWP until it gets to 20 years like the others.

please PLEASE don't limit CEP2 on machines that only run it! Don't let the prospect of adding it for Windows limit it's ability for Linux where it's been working fine....

Please don't kill my crunching because windows is such a piece of junk!

Does this have to be done for Linux, and does it have to be done now, before even being released for Windows?

A few days notice would have at least shown some courtesy to the crunchers. Finding out that changes have been made retrospectively shows tactlessness.

Perhaps change it for Linux users; many of whom put together Linux systems just to run CEP2.

On the most powerful systems (6core AMD, 8threaded and 12threaded Intel, dual and quad skt systems), this would mean limiting what those systems can crunch for CEP2 to 1/6th, 1/8th, 1/12th, 1/24th...

Restricting this project to one core/thread also undermines the idea that people can crunch what they want. Now they must run other tasks too. There are enough terms and conditions already.

Crunchers are resourceful and there are many ways of forcing the system to get more CEP2 work. The people that might do this would be the more regular forum users, who have setup crunching rigs.

Another consideration is bandwidth. Not all systems will be capable of supporting this project. I would hate to see Schools, Universities, businesses with many computers try to run this project. The bandwidth would be too high (especially upload), and they would have problems. On the other hand, home crunchers with dedicated crunching rigs, with more cores/threads have better bandwidth per system. Allowing them to run more tasks would mean less initial file transfer (200MB or 300MB) and would therefore be more efficient for the WCG servers. These are the people you should be encouraging to crunch CEP2 not restricting.

Are there any other Clean Energy Projects elsewhere? I don'€™t run many FA@H tasks here as I do a lot more elsewhere.

Hi X-Files 27,
that doesn't work for me. The 2nd instance (fresh installed in a new working directory) is working, but it is not showing under devices and doesn't get a CEP2 work unit. Seems like the boinc server is clever and recognises this cheat

Fredski, this thread is really about the CEP2 Scheduling change, not the Beta or I/O issues. Guess you just posted here by mistake.

Could the core use just be halved, saying as we could do this anyway.

Would these restrictions prevent users with single core systems running CEP2?
If not, and we can cache CEP2 WU's some users might just crunch CEP2 tasks, and abort or suspend other WCG tasks. Just resuming before an update. Hardly what we would want.