Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 1082. (Read 3426947 times)

For those who can't use the mega.co.nz link, here's the 2013-10-10 version:
http://sonstiges.org/cudaminer-2013-10-10.zip

Btw, 130 kh/s with -i 0 -C 2 -l K80x2 on my GTX660

about 10kh slower than the 64bit build and i get launch config F does not validate
but it did choose the best launch config for my card after autotune (560ti)

Haven't tuned it in yet.

cudaminer-src-2013.07.13

60x4

With the new cuda miner auto tuning T127x1 230 k/hash

Everyone using cudaMiner, please post your results here when you are done tweaking your settings: http://www.lurkmore.com/hardware-compare/

I released the 2013-10-10 version just now and updated the cudaminer github repo.

ATTENTION! Kernel launch configs are now named differently compared to the 07-13 release.
Please autotune again to get your new best launch config.

On some Kepler (or even Titan class) devices the Fermi kernels may be a bit better, so also
try passing -l F to autotune also with the Fermi kernel.

Many thanks go to an "Alex" from greece who submitted some CUDA optimizations through
skype and suggested disabling the parallelization of SHA256 on the CPU.

what cudaminer version and launch config did you use?

ouch, i do 270-295 with my 580... well obviously not on winblows

If there is a Windows build (already compiled) I would happily test

GTX 780 285.69 k/hash stock clock.

the changes I made to this repo recently

https://github.com/cbuchner1/cpuminer

seemed to have improved the situation with the stratum parse problem and subsequent freeze of the miner. Anyone care to test?

Christian

+1

Very much appreciated.

+1

Whoops, lot of activity here lately!

I've had the stratum_recv_line problem for the first time ever. Happened while stratum mining on coinotron.com.

Maybe I can change the code so that it takes the same action as if the stratum connection had timed out.
It would then simply reconnect.

Christian

function blah uses too much shared memory i think was the error i got

Hint: compile for "compute_10,sm_20" instead of "compute_10,sm_10"

Thanks, that worked well on my GTX460.  Bumped me up to 117KH even though the "auto-config" said I should get 140KH.

Although I had issues with -i 1.  When that was enabled I would only get 50% usage on my card except during auto config.  Also to get the best speeds I had to drop -C to 0.

Same, went up to 119KH while my previous max was about 105-115KH.

so guy used cuda 5.5 to build ? i had problems doing that and gave up and went with 5.0 for a 64bit build
kept getting errors compiling on Visual Studio.. about the register usage etc

also i haven't seen that time out error for a looong time.. last it happened was like once, a month ago
not sure what the deal is with that if its the server or a network thing or what
i was using bad net drivers for ages until i figured out using the default windows 7 one cleared it up for good.
i had corrupted data on downloads via Firefox with or with out a download manager a lot from File locker services (all of them)
and also severe corruption i noticed downloading video's on torrents and it magically all went away after struggling with it for years
and so did my miner time out problem.. coincidence ?
failed to parse means there was an error.. not a big deal but if your miner freezes forever afterwards THEN you got a problem lol
So if you see that *rarely but can keep mining i wouldn't worry about it

maybe i will release my mod *publicly i have been sharing it privately and done a lot of new stuff and fixes tweaks etc such as extensive color usage.
people can pm me for a SSE4.1 (Windows 7 tested) build if they really want my version..

also beware a scumbag at The Pirate Bay has been uploading a virus packed / coded into cudaminer in a torrent.

Thanks for that hint  

@fruittool

Also thanks to you. Your miner brought me +4 KH/s. First had problems with cudart64_55.dll missing. I found it in the cuda Setup and extracted it with 7zip. Works fine now.

Yes, that is a common issue with the latest version.  Go back about 4-5 pages to read up on that issue.  I switched back to the 4/30 version.

fruittool

cool i did that too already and it sped things up just building for x64