Re: CUDA 2.2 rates with the new 512 (Beta8) clients.

Kevin G. McCoy wrote:

GTX 275, stock clocking:

dnetc v2.9105-511-CTL-09070517-*dev* for CUDA 2.1 on Win32 (WindowsNT 5.1).
Using email address (distributed.net ID) 'kgmccoy<atsign>idk-inc.com'
[Aug 02 21:55:14 UTC] nvcuda.dll Version: 6.14.11.8618
[Aug 02 21:55:14 UTC] Automatic processor type detection found
a GeForce GTX 275 (30 MPs) processor.
.
.
.

[Aug 12 11:46:59 UTC] RC5-72: Summary: 41 packets (7430.00 stats units)
0.09:28:25.89 - [322.75 Mkeys/s]

Take that, PS3! ;-)

My old NVIDIA GeForce 8600 GTS runs at about 75 Mkeys/Sec w/stock clocking.

Best regards,

Kevin G. McCoy

Joseph Kaye wrote:

I am currently getting:

9800GT ~150Mkeys/s Stock clocks
9600GSO ~142MKeys/s 690MHz GPU 800MHz Memory 1725Mhz Shader
8400GS ~10MKeys/s 700MHz GPU 450MHz Memory 1728MHz Shader

I'm interested to see where the GTX200 series cards fall. If you have
one, can you post your average rate? if you're overclocking, can you
post your settings too?

Thanks!

--Joseph
_______________________________________________
rc5 mailing list
rc5-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected]
http://lists.distributed.net/mailman/listinfo/rc5

_______________________________________________
rc5 mailing list
rc5-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected]
http://lists.distributed.net/mailman/listinfo/rc5

Hey Kevin - you need to update that client! :D

http://n0cgi.distributed.net/cgi/dnet-finger.cgi?user=bovine

:: 27-Jul-2009 03:02 GMT (Monday) ::

Dear friends,

We have discovered our nVidia CUDA clients prior to v2.9105.512 had a

problem that would cause RC5-72 results to skip part of the

block. This issue turned out to be caused by a bug in the CUDA

compiler itself, which was fixed beginning in the CUDA 2.2 SDK. Going

forward we will only be releasing clients for CUDA version 2.2 and

higher.

The fixed behavior unfortunately reveals that new CUDA clients will be

about half the speed of the older buggy CUDA versions. We understand

that the apparent speed decrease will seem disappointing, but it's

important to note the earlier speeds were not measuring useful

work. Going forward, speed comparisons should only be made with CUDA

2.2 or higher speeds, as these are the "correct" speeds. Also, please

remember the CUDA clients are still much faster than traditional CPU

clients.

If you are still running a CUDA beta client, we encourage you to

update to the current versions available on our pre-release page:

http://www.distributed.net/download/prerelease.php Results returned by

any earlier clients will no longer be accepted by our keymaster. Users

with prior stats credit from affected clients will not be

retroactively removed.

Due to aspects of our network communication protocol, we are not able

to remotely shutdown only the older, buggy, CUDA clients so we will be

implementing a method to send large, dummy blocks to older CUDA

clients instead.

Since all dnetc CUDA versions released so far have only been "beta"

clients with built-in expiration dates, the impact should be

contained. The last round of beta CUDA clients would have expired at

approximately the end of August 2009.

Thanks again to all of our beta testers that have been helping us

validate this exciting new technology.

_______________________________________________
rc5 mailing list
rc5-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected]
http://lists.distributed.net/mailman/listinfo/rc5