Of course I have a password.

Please god damned read my thread. IT WORKS WITH 12-18 and any other god damned miner. But not your newer version unless I open / close the folder each time. Why are you being such a prick? Honestly. I'm not the only one with these problems, others are posting about them, but you act like we're all idiots and couldn't, possibly, be your programs fault.

It could be really slow sometimes. I was thinking about trying to add a few lines to cudaMiner --benchmark mode so that it exits after autotune finds the best startup config and make a massive batch file with all the different kernels/lookup gaps/N factors and just let it play while I'm at work. Not sure if the GPU would like to jump up and down all day though.

performace-wise, GT 710 is at the low end...

The current github cudaminer version with the "Y" Kernel will give you the most performance, I guess. That is assuming it's a Kepler part... (not sure)

Christian

the communication was so far limited to a kernel submission from nVidia.

It's a high register count (1 hash per thread) Compute 3.5 kernel that gives some marginal improvement over Dave Andersen's work. Unfortunately it's not well suited for implementing a LOOKUP_GAP.

Christian

Yeah, you can donate to YBQ4hrUQqEb2EDip1NFwMAgZbvK8hJx5Tn

Good idea about starting a new thread for the scrypt-jane enabled cudaminer, once it is released.

I have made some changes to autotune reliability and speed. It will not assign less blocks than half the multiprocessor count in your card. For example on a GTX 780 it will start autotuning at 6 blocks now (the card has 12 SMX).

Also I made changes to how memory is allocated. The backoff value on Windows is currently 12% of the largest allocation it was able to make. On Linux it is a mere 2%. If I don't back off, autotune will crash pretty badly. It can still occasionally crash with launch timeouts though.

I find that my GTX 660Ti is a better investment than my new GTX 780 card (3 GB each, but 7 vs 12 SMX). At -L 2 the 660Ti totally beats my 780. Meh.

My GT 660 Ti uses -L 2 -l K64x2 -C 1 -b 32768 -i 0 and gets 3.7 kHash/s

Christian

Should we roll the Lookup-Gap into kernel launch configurations?

I am also considering to also allow specifying the devices like in the following example because whenever I swap cards around on my mainboards, all the device IDs get shuffled by CUDA which is annoying. The strings however would keep working as is, unless you remove the card with the given name.

-d "GT 640, GTX 780 Ti, GTX 660 Ti, GTX 660 Ti#2"

Christian