Is anybody having problems running more than two GPUGRID WU's (whether they are the long or short runs and the combinations thereof) with dual GTX 590's? It seems when the third WU kicks in, the client comes to a very slow crawl. Combinations of thw two GPUGRID WU's and other project WU's seem to work fine, as well as up to four non-GPUGRID WU's crunching at the same time (as I have been for months before adding the GPUGRID project...)

The two GPUGRID WU's work fine whether they are running on one GTX 590 or split between the two GTX 590's. But, again, when that third GPUGRID WU kicks in, the client crawls to almost a frozen state. Closing the client returns the OS to normal operation. Restarting the client presents the same results...

Hi: Unfortunately I can not give answer to your problem.

What I can assure you that the performance of the GTX590 is very low, pay less than my GTX295.

I have been comparing their execution times and are even higher with my GTX295 ... incomprehensible.

You may have a problem with the ports PCIe (x16 or x8)

Let us also mention that the hyperthreading is not suitable for these compute-intensive tasks. Greetings.

Thanks much for the hyperthreading advice! It seems GPUGRID did not like it...

I am now running GPUGRID full blast on my GPU's without any issues.

A shame about the performance differences between the GTX 590 and GTX 295. It's one of those give and take situations, I guess! ;o)

What I can assure you that the performance of the GTX590 is very low, pay less than my GTX295.

I have been comparing their execution times and are even higher with my GTX295 ... incomprehensible.

Let us also mention that the hyperthreading is not suitable for these compute-intensive tasks.

Is anybody having problems running more than two GPUGRID WU's (whether they are the long or short runs and the combinations thereof) with dual GTX 590's? It seems when the third WU kicks in, the client comes to a very slow crawl.

It seems turning hyperthreading off is much more forgiving, but the issue still crops up...

After turning off system overclock settings and turning hyperthreading back on, the problem goes away completely! I've been running all other projects with the OC'd settings for months (pre-GPUGRID). I guess I have some more tweaking to do...

By the way, I was running dual X5650's (2.67GHz) Xeons @3.6GHz on an eVGA SR-2 Series 5520 motherboard.

Thanks for all the GPU stats and feedback, folks!

You messed up this comparsion.
Your GTX 295: I44R2-GIANNI_KKFREE5-22-100-RND0060_1 GPU:55843s CPU:8542s
My _ GTX 590: I199R0-GIANNI_KKFREE5-26-100-RND0232_0 GPU:29524s CPU:4959s... etc...

It seems turning hyperthreading off is much more forgiving, but the issue still crops up...

After turning off system overclock settings and turning hyperthreading back on, the problem goes away completely!

I've been running all other projects with the OC'd settings for months (pre-GPUGRID). I guess I have some more tweaking to do...

By the way, I was running dual X5650's (2.67GHz) Xeons @3.6GHz on an eVGA SR-2 Series 5520 motherboard.

Thanks for all the GPU stats and feedback, folks!

Test Folding with you 590,

https://fah-web.stanford.edu/projects/FAHClient/wiki/BetaRelease

@+
*_*
____________

Well... I reverted back a few BIOS revisions after chatting with fellow SR-2 builders. It seems BIOS A46 (June 2010) is the magic release for my use. The OC'ing seems stable at 3.6GHz...

Also, I was clued-in on SLI mode being a culprit as well after I installed a 5th GPU into the system (latest graphics driver allows for up to a 4-way SLI + an extra GPU for PhysX). When the 4 GPU's were having problems, the lone PhysX GPU was happily crunching away. I turned off the SLI mode and now all 5 GPU's are running fine for the time-being. It seemed when the CPU's are relatively busy, even at 85%, the GPU's had a hard time starting the GPUGRID WU's. Now, I have everything running 100% with no problems so far with any of the WU's...

Here's hoping that the issue has been resolved!

Thanks, again, everyone!