IMHO this should have been launched as a separate project, but as it's not I'd like to suggest having a separate league table on the dashboard for the CPU tasks. As it is, anyone just running CPU tasks is basically invisible in the project.
regards

Maybe I misunderstood the plan but I thought there was going to be a separate project?
As anticipated there are issues with supplying both CPU and GPU work to clients attached to other projects (which is just about everyone).
Will 'Scientific Publication Badges' be awarded against CPU contribution and will there be any mutual CPU and GPU work? If so there could be a lot more plastics out there ;p...
I also agree with having a separate credit system, but again, I think it would be best done via a separate project.
Obviously the main concern is the project management overhead, so if you think it's too much to do on a different project then so be it.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Will 'Scientific Publication Badges' be awarded against CPU contribution and will there be any mutual CPU and GPU work? If so there could be a lot more plastics out there ;p...

Yes, most likely we will award badges for that work.

I also agree with having a separate credit system, but again, I think it would be best done via a separate project.

I'm looking into the possibility of having a separate league table for CPU crunching.

Matt

I also agree with having a separate credit system, but again, I think it would be best done via a separate project.

We should name it CPUGrid :)
To be a little ahead of future events (when a proper OpenCL application will come out) a third project should be created called APUGrid.
Just kidding.
But seriously the main reason I've disabled CPU work from GPUGrid is that I want to crunch for other (CPU only) projects also, and the credit comes from CPU work is negligible compared to the credit comes from GPU work. To attract more CPU crunchers, the credit comes from CPU work should be much more distinct from the credit comes from GPU work. I agree with Stoneageman: the best would be a different project for it. However I'm not sure that your infrastructure can handle the increased network traffic and data processing on your servers caused by 100000 new hosts on a new project.

A side effect of putting CPU contributions in the paper badges (something I would consider natural) would be that CPU-only users will be numerous but rank low - therefore pushing up GPU users. Not sure it is a bad problem.

We should name it CPUGrid :)
...the main reason I've disabled CPU work from GPUGrid is that I want to crunch for other (CPU only) projects also, and the credit comes from CPU work is negligible compared to the credit comes from GPU work. To attract more CPU crunchers, the credit comes from CPU work should be much more distinct from the credit comes from GPU work. I agree with Stoneageman: the best would be a different project for it. However I'm not sure that your infrastructure can handle the increased network traffic and data processing on your servers caused by 100000 new hosts on a new project.

My Wish is to have CPUGrid be separate from GPUGrid. I'd like to run some of your CPU WUs but not on every single computer that I run GPU WUs on. It's all or nothing the way it's configured now. So I had to pick NO CPU WUs.

You could look to Primegrid how they handle their badge system, badges for each subproject but all in the same credit pool. Works very well there I think.
People can choose which subprojects they want, and make some milestones in each. But probably not easy to set up.

Aurum, can't you make different "venues" here, like "school", "work", "home" etc, for the settings? Run some with CPU only some with GPU only, and some with both for example.

(there is an error on that preferences page, but it will still save settings)

(Ryle), I guess I could but with 36 computers it would be a nightmare. I do as little as possible from the server side.

I tried again for the last few days to turn on CPU WUs. But they do not play nice with other kids. So I had to turn it off.

I Wish that CPUGrid was separate from GPUGrid.

I'd like to run some of your CPU WUs but not on every single computer that I run GPU WUs on.

It's all or nothing the way it's configured now.

So I had to pick NO CPU WUs.

I'd like to run some of your CPU WUs but not on every single computer that I run GPU WUs on.
It's all or nothing the way it's configured now.
So I had to pick NO CPU WUs.

Maybe I'm not understanding what you want to do, but you can configure different profiles in project preferences (Default, Home, Work, School) with different choices. Then assign machines as you like to those profiles.

I've got 38 computers and there's no way I'm going to add that complication to the mix. Besides, My Account has errors, etc.

CPU projects need complete autonomy from GPU projects.

Until then I will not be running any more GPUGrid CPU WUs. Same for other projects.

Hi:

I have an Alienware desktop with an i7-8700K CPU and a NVIDIA GeForce GTX 1070 video card. I am getting plenty of workunits to keep my CPU busy but 2 workunits for my video card is not enough. I would like more.

Would it be possible to add an option for user defined quantity of workunits for the GPU to work on. The other option would be to increase the default daily allowance of GPU workunits.

Clive
British Columbia, Canada

Daily limit is increased once tasks are completed. There are not enough tasks anyway.

Daily limit is increased once tasks are completed. There are not enough tasks anyway.