i give up

They have really done everything that BOINC is a pain for me!

• Not installable on DomainController -> workaround: old version.
  
• Not usable on DomainClients -> workaround: unsecure Host so BOINCsecurity works.
  
• Cache not per project -> workaround: a lot of timeconsuming babysitting
  
• not possible to dedicate project to core/cpu/gpu -> workaround: a lot of timeconsuming babysitting and messed up systems
  
• scheduling is a bad joke -> babysitting, babysitting and babysitting
  

I managed to have a RAC of 130,000 when 180,000 were possible without BOINCs control and 80,000 or less were realistic without my control.

I pay about 200€/Month only for the BOINC part (CPU/GPU at 100%) not including the base costs to run all systems 24/7.
What i get back is the statement that there will be no hope for a better situation as they keep their goal to control everything and let the user as less as possible control over their own systems.

But the reason is not RAC, time or money - it's the feeling to get kicked for my efforts!

I've set all my hosts to not receive new work and in 1 to 20days when the 10day caches are empty, i'll uninstall all BOINC.

Sadly i take 3 users with me as i babysitted their systems what they don't want to do for their own and i suspect that another 2 will follow in a few days when they run into first trouble with BOINc on their own.

Perhaps i'll come back when BOINC gives control over my systems back to me - where it belongs!

Goodbye
Holger

I'm sorry that Boinc doesn't meet your specific expectations. It was designed for the million of peoples that wish to contribute their spare CPU cycles to science with a minimum of tinkering. It was not designed for the few thousand that want to control every aspect of the software and that are more interested in their RAC then the contribution to science.

Boinc was never intended to be micromanaged and never will be. None of the projects expect people to babysit the software or spend extra money buying dedicated crunchers. This is a decision made by you and is not a concern of Boinc or the scientific community that uses its software.

I feel that the developers made some poor choices concerning the scheduler with the precipitous introduction of CUDA capability in V6. I personally think that the V5 scheduler had reached near optimal performance and was quite acceptable. Boinc definitely took a step backwards with its redesign. Hopefully the developers will be guided by user suggestions and the current scheduling problems will soon show improvement. Just leaving Boinc out of frustration is not being very constructive. Continued participation with thoughtful feedback is.

Making Boinc secure for the majority of users from rogue elements was a primary concern. Secure Domain Controllers installation presents a specific challenge and that issue will be addressed in the next couple of major releases.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470