Not sure how well the CPU/GPU preference is going to work with the BOINC scheduling issues.

For one thing, I do not wish to have the same resource share for the CPU and GPU.

We will be releasing a cpu app soon. It will only provide a small number of WUs as it is complementary to our main application and it is supposed to serve people who does not have a gpu.

The idea is that you will be able to opt out of the cpu application.

We are not sure how this will work. So, comments are welcome.

gdf

I recommend to make that 'opt-in'. I do not want to have CPU apps using memory that is maxed out speed-wise by the GPU apps already. That is the reason why GPUGrid is the only project running.

Instead I'd very much would like an option that allows a 'number of CPU+n' queue instead of 'number of CPU'. I very often find one or more of my GPUS idle because only the upload of the next result will trigger the acknowledgement of the previous one, despite the 'report results immediately' flag. Meanwhile the idling can take hours. Even if n would be only one, it would much help to streamline my crunching.

---

Join team Bletchley Park, the innovators.

I do not want to have CPU apps using memory that is maxed out speed-wise by the GPU apps already.

Are you sure about that? Seriously, it does sound strange. Each GPU needs assistance every couple of ms, whereas your memory runs at ns. Does changing your main memory speed impact your GPU performance?

MrS

---

Scanning for our furry friends since Jan 2002

We will be releasing a cpu app soon. It will only provide a small number of WUs as it is complementary to our main application and it is supposed to serve people who does not have a gpu.

The idea is that you will be able to opt out of the cpu application.

We are not sure how this will work. So, comments are welcome.

gdf

You could ask SETI@HOME as they have this option.

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

We will be releasing a cpu app soon. It will only provide a small number of WUs as it is complementary to our main application and it is supposed to serve people who does not have a gpu.

The idea is that you will be able to opt out of the cpu application.

We are not sure how this will work. So, comments are welcome.

gdf

..

Couple questions:

It sounds like these will be different WU's than those crunched by the GPU's is that right?

How long do you anticipate the CPU WU's to run (a rough estimate based on internal testing and machine speed for that time)

I like the idea, though definitely appreciate the heads up before issuing tasks. Currently throttling all CPU's at some other goals at the moment, but might give them a try after those goals are met.

Only suggestion would be to perhaps have Use CPU option as "No" by default, as many do not visit the forums or the site frequently, and might get a bit peeved if they suddenly notice CPU tasks on their machines.

Only suggestion would be to perhaps have Use CPU option as "No" by default, as many do not visit the forums or the site frequently, and might get a bit peeved if they suddenly notice CPU tasks on their machines.

A very valid point. But I guess in thast case not many people would run the cpu app at all, wouldn't they?

MrS

---

Scanning for our furry friends since Jan 2002

so, are you going to have to change the project name again now that we'll have PS3's, GPU's, and CPU's?