[ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX]

[djm34]

yes it could be interesting (I bought by mistake when I started mining an usb asic, currently getting scrap of uno on coinex... if it could contribute to something more useful).

[1714553412]

1714553412

[1714553412]

1714553412

[1714553412]

1714553412

[1714553412]

1714553412

[1714553412]

1714553412

[1714553412]

1714553412

[manofcolombia]

What the heck happened with microcoin? I started up the miner today and now I'm getting 160 khash with both my cards where the other day I was at 600. Did the N-factor go up? Because last I looked network difficulty was at 5.5 but today its down to around 3.2?
However, I am liking the prices ate Poloniex...wish I would have kept a few more when I was selling them at .00000140 ltc :/

[whitesand77]

What the heck happened with microcoin? I started up the miner today and now I'm getting 160 khash with both my cards where the other day I was at 600. Did the N-factor go up? Because last I looked network difficulty was at 5.5 but today its down to around 3.2?
However, I am liking the prices ate Poloniex...wish I would have kept a few more when I was selling them at .00000140 btc :/

Yes, N factor went from 9 to 10 today.  Had to re-tune my cards this morning.  Cudaminer took the change just fine but the kernel settings were not optimized for the new N factor.

[manofcolombia]

What the heck happened with microcoin? I started up the miner today and now I'm getting 160 khash with both my cards where the other day I was at 600. Did the N-factor go up? Because last I looked network difficulty was at 5.5 but today its down to around 3.2?
However, I am liking the prices ate Poloniex...wish I would have kept a few more when I was selling them at .00000140 btc :/

Yes, N factor went from 9 to 10 today.

Jeez well thats a massive decrease in hashing speed. A major downer looking at the console now :/
Since the N factor was raised and now more memory is needed doesn't that mean that cpu mining should be more effective since we can pile in more memory for a cpu to utilize?


Ah! Autotuning again with the new N factor helps. I'm up to 295 khash both combined. Now that feels allot better.

[djm34]

if it works like for the previous nfactor increase the difficulty should go down soon...

[debido666]

Would go well with some Mars cards. Hint hint.

http://www.pcworld.com/article/2099945/meet-dopamine-the-6-gpu-case-designed-for-bitcoin-miners-and-pc-enthusiasts.html

[djm34]

Would go well with some Mars cards. Hint hint.

http://www.pcworld.com/article/2099945/meet-dopamine-the-6-gpu-case-designed-for-bitcoin-miners-and-pc-enthusiasts.html

look nice, but something tells me it won't be cheap...

[see360]

EDIT: outdated info

[djm34]

Regarding MRC N-factor change, I had a strange thing happen. I was pool mining with two 660ti overnight (after the N factor change) with -l K7x32,K7x32, and they were happily getting yays from the pool this morning. When I saw the price of MRC, I added my 780ti to the bat file. The moment I restarted mining, I got validation errors on both of the 660ti GPUs. Tried running the bat file (which had been running the two 660ti just fine 5 minutes before) but now that got validation errors as well. To avoid the errors, I am now running the lower case t and k kernels instead of the T and K. Curious.

well, not that curious, otherwise you would have read all the previous messages...

[Mav2000]

ANyone try blackcoin with cuda? I am getting around 150khash with a 770gtx. Is that normal?

[see360]

Regarding MRC N-factor change, I had a strange thing happen. I was pool mining with two 660ti overnight (after the N factor change) with -l K7x32,K7x32, and they were happily getting yays from the pool this morning. When I saw the price of MRC, I added my 780ti to the bat file. The moment I restarted mining, I got validation errors on both of the 660ti GPUs. Tried running the bat file (which had been running the two 660ti just fine 5 minutes before) but now that got validation errors as well. To avoid the errors, I am now running the lower case t and k kernels instead of the T and K. Curious.

well, not that curious, otherwise you would have read all the previous messages...

I have read every message on this board from page 1. The curious part that hasn't been pointed out is that the -l K7x32 config ran fine after the N factor change, but then didn't run after restarting today.

On another note, there are several settings that give me almost the same results (t24x32, t25x32 t30x32 are almost all the same) because my cards are temperature bound.

EDIT: Didn't mean for that to sound snarky djm34. Your posts have been very helpful to me over the last several months.

[whitesand77]

Anyway, -b doesn't seem to change anything, and -L higher than 1 is slower for me.

That's because MRC is at N factor of 10 which is a max batch size of 2048.  Default batch size is 1024 FYI.

So when Cudaminer goes to launch the kernel it looks at N factor and your -b batch setting and uses the minimum of the two.

[DeltaQuebec]

Hello everyone, Ive been pretty good @ getting cudaminer to work on most different algos, but I've run into a block with CACHE coin..  here is my .bat

cudaminer32.exe  --algo=scrypt-jane:CACH -L 2 -o stratum+tcp://east1.us.stratum.dedi................

The cudaminer window opens very fast & shuts down. I'm probably overlooking something easy, but I cant figure it out, I have read the read me doc 5x now   Any help would be great!

[debido666]

Anyway, -b doesn't seem to change anything, and -L higher than 1 is slower for me.

That's because MRC is at N factor of 10 which is a max batch size of 2048.  Default batch size is 1024 FYI.

So when Cudaminer goes to launch the kernel it looks at N factor and your -b batch setting and uses the minimum of the two.

https://docs.google.com/spreadsheet/ccc?key=0Aj3vcsuY-JFNdC1ITWJrSG9VeWp6QXppbVgxcm0tbGc&usp=sharing#gid=0

[see360]

Hello everyone, Ive been pretty good @ getting cudaminer to work on most different algos, but I've run into a block with CACHE coin..  here is my .bat

cudaminer32.exe  --algo=scrypt-jane:CACH -L 2 -o stratum+tcp://east1.us.stratum.dedi................

The cudaminer window opens very fast & shuts down. I'm probably overlooking something easy, but I cant figure it out, I have read the read me doc 5x now   Any help would be great!

There probably isn't an executable file in the directory named cudaminer32.exe, so the cmd window just shuts thinking it's executed everything there is to do. Try changing cudaminer32.exe to cudaminer.exe ...

[DeltaQuebec]

Hello everyone, Ive been pretty good @ getting cudaminer to work on most different algos, but I've run into a block with CACHE coin..  here is my .bat

cudaminer32.exe  --algo=scrypt-jane:CACH -L 2 -o stratum+tcp://east1.us.stratum.dedi................

The cudaminer window opens very fast & shuts down. I'm probably overlooking something easy, but I cant figure it out, I have read the read me doc 5x now   Any help would be great!

There probably isn't an executable file in the directory named cudaminer32.exe, so the cmd window just shuts thinking it's executed everything there is to do. Try changing cudaminer32.exe to cudaminer.exe ...

BINGO! Thank you so much! ( will fine tune stuff now )

[djm34]

Regarding MRC N-factor change, I had a strange thing happen. I was pool mining with two 660ti overnight (after the N factor change) with -l K7x32,K7x32, and they were happily getting yays from the pool this morning. When I saw the price of MRC, I added my 780ti to the bat file. The moment I restarted mining, I got validation errors on both of the 660ti GPUs. Tried running the bat file (which had been running the two 660ti just fine 5 minutes before) but now that got validation errors as well. To avoid the errors, I am now running the lower case t and k kernels instead of the T and K. Curious.

well, not that curious, otherwise you would have read all the previous messages...

I have read every message on this board from page 1. The curious part that hasn't been pointed out is that the -l K7x32 config ran fine after the N factor change, but then didn't run after restarting today.

On another note, there are several settings that give me almost the same results (t24x32, t25x32 t30x32 are almost all the same) because my cards are temperature bound.

EDIT: Didn't mean for that to sound snarky djm34. Your posts have been very helpful to me over the last several months.

Try to rerun the autotune, I did that when the UTC moved to Nfactor 10 last week, it works okay.
You should also use -L2, you should gain some khash/s compared to the default setting (-L1)

[chapmanjw]

@cbuchner1: Is it possible to set the "intensity" for CudaMiner like cgminer and other GPU miners?  When I am doing other things on my machine, it would be nice to have a way to lower its resource utilization.

[bzyzny]

I see in OP it says Dev is considering adding Blake support, I just wanted to say this would be greatly appreciated!!

[eLeMe]

@cbuchner1: Is it possible to set the "intensity" for CudaMiner like cgminer and other GPU miners?  When I am doing other things on my machine, it would be nice to have a way to lower its resource utilization.

-i 1 = useable pc
-i 0 = somewhat useable pc