... I should be able to double, or maybe tripple up and see huge gains ...

Not happening. GPUs are only designed for the execution of one program at a time, it cannot multitask like a multi-thread CPU. That will change with AMDs new architecture which will give that ability, however, on anything less than 7XXX, it will not.

What happens is .... it will load 2... 3 WUs, whatever you give it (it will choke on four), and then divide time equally between the loaded WUs, net result is no gain, for (say) two WUs it takes twice as long to crunch, with the net result of the same time per WU.

With very small WUs (aka milkyway), you can get a gain of about 2-3% by loading two per GPU as you save time in the load/unload/windup of each WU. It can be hassle as well, so horses for courses as to whether or not its worth it even at MW.

.... but here .... not a chance, dont waste time trying, it will not work the way you anticipate.

Regards
Zy

Hi,

I don't think scheduler expects people to try to use half ATI card and might actually crash. I'll have to take a look so that it won't at least crash..

Why are you trying to use two tasks on one card? I highly doubt it'll be twice as fast since both of them will use the same card (at full speed) and D.Net Client might even get so tangled that it can't finish correctly.

-w

Hi,

There's an example 32-bit Windows ATI cruncher app_info.xml available at http://moowrap.net/download/app_info-win32-ati14-example.xml. It might be usable as is except ATI card <count> field might need adjusting.

Also <flops> field value is based on my own host and you should probably copy actual value for your host from your client state file. (The value gets calculated for each host by BOINC.) You can also try without one if you can live with funky estimates until BOINC sorts itself out. :)

-w