Does this make Nvidia cards realistic for mining? OR are they still underperforming comparatively?

At the low end of the performance spectrum, the 9500GT in my work computer's getting about 7.5 kH/s. It leaves my system fairly unresponsive, though.  With something like cgminer, you could back off the intensity to get acceptable desktop performance on a system that's not dedicated to mining.  Is there a similar option here?  I didn't see anything in cudaminer -h or in a quick perusal of the source code.  I have a config file set up, but it currently only has algo, url, and user options defined.

I'm not expecting any miracles performance-wise, but if I could squeeze out a few more coins without impacting this computer's normal functions, that would be nice.

Card is a GTX 560 Superclocked, herehttp://www.amazon.com/gp/product/B0050I1PGU/ref=oh_details_o01_s03_i00?ie=UTF8&psc=1.

1024MB of RAM, and yes, using the 306.97 driver stack.  Windows 8 is the OS.

there is a --no-autotune switch if this feature doesn't do much for you, or if you need to restart your miner once every few minutes ( other than for configuration set up, I don't see any need for so many restarts ).

Also look at the above screenshot to see how it is expected to be working. I guess in your case the Autotune simply wasn't done yet when you aborted. Generally, the more memory is on your card the more combinations autotune will attempt. The LONGPOLL detection will occasionally output messages even during autotune.

Christian

I haven't optimized for Titan yet. I expect a single card could do 300kHash/sec when using the new Funnel Shifter hardware feature.

I hope you bought them for gaming, not for mining

cbuchner1: It works fine with my nvidia card - 50Kh/s 
But WHY IT DOESN'T MINE SHARES on pool?  Console window shows "accepted" messages but my pool shows that your miner doesn't mine any shares(worker has 0 kh/s, while cpuminer's worker has 10kh/s)

When you planning to release real working(shares mining) version of cudaminer?

EVGA GTX 570, getting just shy of 140 KH/s on each solve. Initial auto config gave me something around 170KH/s when I started it up.

GeForce driver: 314.22
EVGA Precision settings: GPU 910MHz; Memory 2100 MHz; 1025mv (If you guys have suggestions for changes to these settings, I'd love to hear them.)

--> EDIT: I almost forgot, my temp stayed between 69c and 70c which is 4c to 6c cooler than reaper, and 5c to 8c cooler than btc mining. Which is nice. <--

-------------

First of all thank you for working on this, I've been playing around with Reaper for the last few weeks attempting to find the sweet spot in the config. The best I got was just shy of 90KH/s. With that said, it took me a hot minute to figure out how to set this up since the readme file didn't say anything. lol. My suggestion would be to add some info about that, and other functions for those of us switching to this from reaper, or other non CGminer type miners. Along with a little background about the other required programs. My only real request at this moment would be a graceful shutdown feature like what reaper has, where it doesn't crash the driver.

My observations were that I really couldn't use anything else while this was running. Firefox took minutes to respond, often switching to "not responding" or otherwise hanging. So my habit of watching Netflix while letting reaper and scryptminer-gui run is now broken. Speaking of scyptminer my blond moment was not turning it off during my initial run of this program (the numbers above are from the second run). The only oddity was that print-screen didn't capture anything.

Other system info:
i7-2600K @ 3.8
16GB RAM
Win7 64-bit

Hi all,

today I've been refactoring the CUDA kernels. I was able to cut shared memory use in half and also lowered the register use. This leads to higher occupancy on the multiprocessor units, resulting in higher speeds !

GTX 460 now solving 80 kHash/s (previously around 62-64). I will give it a spin on more nVidia devices I own, and within a short time frame you can expect an update. EDIT: With the same optimization the GTX 260 performance goes down from 42 to 31 kHash. Meh.

MrLetter: you will soon get even more kHash out of the GTX 570. I believe the CPU is stealing those 30 kHash/sec because it has to do the HMAC 256 part of scrypt. And once the CPU core is 100% pegged, it can't provide the GPU with work units fast enough. I will have to include the SSE2 optimized assembly code from cpuminer to fix this.

wndrbr3d: pass the --no-autotune option please or wait a few minutes more... It could also be stuck at requesting a LONGPOLL connection with the pool. Longpoll can be disabled in options, too.

Some of you really want to use their desktops while mining. We can have that, but it will slow down your kHash/sec of course...

Christian

Still no bueno, although you're getting closer This version doesn't crash on start up, but now it just seems to not mine. Not entirely sure yet.

Here's what I see happening in GPU-Z:



GPU load seems to go up and down some while the host CPU (i5-3570) gets pegged. Perhaps an issue with the CPU not being able to feed the massive amounts of SP's with the SHA256 calc happening on the CPU?

Dove into the code and I think there's something going on with the chunked memory allocation routine in find_optimal_blockcount(). I had it log out the warps through the loop, you can see the two threads doing their allocations but things start getting REAAAALLY slow...



Not sure what could cause this. When I set -t 1, it flies through this no problem so I imagine it has something to do with the two GPU threads being kicked off at once.

Hope this helps!