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

[restless]

And a little update.

The good: Managed to squeeze out a decent ~40% buff to hashrate, now pulling 330 W instead of 270 W. Less frequently accessed stuff in global memory and vice versa, no magic there.

Code:

[2014-06-24 07:31:42] accepted: 7/7 (100.00%), 1323.63 H/s (yay!!!)
[2014-06-24 07:31:42] GPU #5: GeForce GTX 750 Ti, 226.77 H/s
[2014-06-24 07:31:42] GPU #3: GeForce GTX 750 Ti, 226.87 H/s
[2014-06-24 07:31:43] GPU #4: GeForce GTX 750 Ti, 226.51 H/s
[2014-06-24 07:31:43] GPU #1: GeForce GTX 750 Ti, 229.07 H/s
[2014-06-24 07:31:44] GPU #0: GeForce GTX 750 Ti, 228.27 H/s
[2014-06-24 07:31:44] GPU #2: GeForce GTX 750 Ti, 227.61 H/s

The bad: The kernel still runs stupid slow and eats up Windows desktops for breakfast, lunch and dinner. And snacks. Lots of snacks, practically nonstop. I did find a launch config with nice balance between hashrate and kernel run time, keeping it below the 2 second TDR timeout and hitting about 200 H/s but it still takes way too long and still pretty much destroys desktop interactivity. Basically run it on another card in your system and leave the one with your display alone or walk away from the computer after starting the miner.

Easy solution - a switch which cards to eat snacks. Like -d 1,2  for sgminer

[djm34]

And a little update.

The good: Managed to squeeze out a decent ~40% buff to hashrate, now pulling 330 W instead of 270 W. Less frequently accessed stuff in global memory and vice versa, no magic there.

Code:

[2014-06-24 07:31:42] accepted: 7/7 (100.00%), 1323.63 H/s (yay!!!)
[2014-06-24 07:31:42] GPU #5: GeForce GTX 750 Ti, 226.77 H/s
[2014-06-24 07:31:42] GPU #3: GeForce GTX 750 Ti, 226.87 H/s
[2014-06-24 07:31:43] GPU #4: GeForce GTX 750 Ti, 226.51 H/s
[2014-06-24 07:31:43] GPU #1: GeForce GTX 750 Ti, 229.07 H/s
[2014-06-24 07:31:44] GPU #0: GeForce GTX 750 Ti, 228.27 H/s
[2014-06-24 07:31:44] GPU #2: GeForce GTX 750 Ti, 227.61 H/s

The bad: The kernel still runs stupid slow and eats up Windows desktops for breakfast, lunch and dinner. And snacks. Lots of snacks, practically nonstop. I did find a launch config with nice balance between hashrate and kernel run time, keeping it below the 2 second TDR timeout and hitting about 200 H/s but it still takes way too long and still pretty much destroys desktop interactivity. Basically run it on another card in your system and leave the one with your display alone or walk away from the computer after starting the miner.

Easy solution - a switch which cards to eat snacks. Like -d 1,2  for sgminer

what happens to the cards which are not plugged to a monitor ?

[DemosMirak]

Gotten some questions via PM so thought I'd head them off in the thread if possible.
1) Can you start testing it now?
A) Soon, if you are interested in being involved in alpha/beta testing before it goes public send me a PM with your rig details.  I'll start to open this up in a few days to additional miners.

Perhaps a bit too early for a feature request, but here goes anyway:

Is it possibly to opt-out of certain coins/algorithms. Let's say that algo A runs fine on my rig, even while using it. I would have no objections to running that algo while I use the rig. Algo B however turns my rig into a unresponsive mining heap. I would have no objection to that if I wasn't using the rig, but if I am using it, I would rather not mine that. Is it possible to build in preferences like that? Not to mention algo C, which is highly unstable on my rig, and crashes it even with underclocks.

Anyway, looking forward to your work.

[cayars]

Gotten some questions via PM so thought I'd head them off in the thread if possible.
1) Can you start testing it now?
A) Soon, if you are interested in being involved in alpha/beta testing before it goes public send me a PM with your rig details.  I'll start to open this up in a few days to additional miners.

Perhaps a bit too early for a feature request, but here goes anyway:

Is it possibly to opt-out of certain coins/algorithms. Let's say that algo A runs fine on my rig, even while using it. I would have no objections to running that algo while I use the rig. Algo B however turns my rig into a unresponsive mining heap. I would have no objection to that if I wasn't using the rig, but if I am using it, I would rather not mine that. Is it possible to build in preferences like that? Not to mention algo C, which is highly unstable on my rig, and crashes it even with underclocks.

Anyway, looking forward to your work.

You will already be able to do this.  Lets say for example Script, The Janes/Chacha or Script-N (basically all the Scripts) give your rig problems for whatever reason.  You could simply enter a ZERO for the hash speed.  So when the client calculates btc earning per day it takes current value from the server and multiplies it times the algo hash speed you entered.  In this case X * 0 = 0 so that algo would not get used.

You could optionally have 2 different configs to run right now by just making a copy of the program and settings.conf file into different directory.  This would allow you to have different "aggressive" settings for when you are or aren't using your computer (if it's your main computer). Certain algos could be set to ZERO this way while others that run fine while using the computer could be used.  Or if using sgminer on AMD cards you could use a different "-I or -X" intensity setting.

Carlo

[tsiv]

I'll just... yea, leave this here:

https://github.com/tsiv/ccminer-cryptonight

Do not motherfscking come to me with complaints about lag on Windows, you have been warned

Guess I'll take a look at breaking the one big kernel into smaller pieces that run sequentially, hopefully giving the OS some breathing room. Should at least help with the TDR problem.

[AizenSou]

LOL everyone offers alpha/beta testing. Make me laugh.  
Did this happen before with Christian?
Stop this guys, this just makes us look greedy in tsiv's eyes. He will opensource this miner when he thinks it's ready. In the meantime, we still have a lot of others coins to mine.  

EDIT: holy cow. He publishes it 3 seconds before my post. You see? LOL

[kqpahv]

I'll just... yea, leave this here:

https://github.com/tsiv/ccminer-cryptonight

Do not motherfscking come to me with complaints about lag on Windows, you have been warned

Guess I'll take a look at breaking the one big kernel into smaller pieces that run sequentially, hopefully giving the OS some breathing room. Should at least help with the TDR problem.

Even though I am a AMD miner with only a few Nvidias -  NICE work  

[djm34]

Gotten some questions via PM so thought I'd head them off in the thread if possible.
1) Can you start testing it now?
A) Soon, if you are interested in being involved in alpha/beta testing before it goes public send me a PM with your rig details.  I'll start to open this up in a few days to additional miners.

Perhaps a bit too early for a feature request, but here goes anyway:

Is it possibly to opt-out of certain coins/algorithms. Let's say that algo A runs fine on my rig, even while using it. I would have no objections to running that algo while I use the rig. Algo B however turns my rig into a unresponsive mining heap. I would have no objection to that if I wasn't using the rig, but if I am using it, I would rather not mine that. Is it possible to build in preferences like that? Not to mention algo C, which is highly unstable on my rig, and crashes it even with underclocks.

Anyway, looking forward to your work.

is this working in solo ?
Also don't forget thate there is a bounty to collect for an open source cryptonight miner 

[djm34]

I'll just... yea, leave this here:

https://github.com/tsiv/ccminer-cryptonight

Do not motherfscking come to me with complaints about lag on Windows, you have been warned

Guess I'll take a look at breaking the one big kernel into smaller pieces that run sequentially, hopefully giving the OS some breathing room. Should at least help with the TDR problem.

Even though I am a AMD miner -  NICE work  

go mine jpc...   there is something new for you there  

[kqpahv]

I'll just... yea, leave this here:

https://github.com/tsiv/ccminer-cryptonight

Do not motherfscking come to me with complaints about lag on Windows, you have been warned

Guess I'll take a look at breaking the one big kernel into smaller pieces that run sequentially, hopefully giving the OS some breathing room. Should at least help with the TDR problem.

Even though I am a AMD miner -  NICE work  

go mine jpc...   there is something new for you there  

Oh you guys rock    Thats a really nice suprise  
Can I create a working bin by copying 14.6 drivers cl files to the miners directory ?
I'll send you a few thousand JPC's still left in my wallet for now and will donate some more later  

[tsiv]

LOL everyone offers alpha/beta testing. Make me laugh.  
Did this happen before with Christian?
Stop this guys, this just makes us look greedy in tsiv's eyes. He will opensource this miner when he thinks it's ready. In the meantime, we still have a lot of others coins to mine.  

EDIT: holy cow. He publishes it 3 seconds before my post. You see? LOL

I'm doing this the Microsoft Way (tm). "If it more or less works, launch it. Maybe fix some huge problems with it sometime next year, if enough people complain long and hard enough. Maybe."

[Burninj]

Hey any nvidia insiders who can hint us when gtx 880 is hitting market? have a shitload of btc waiting to buy these babies.

[SRBOOTH]

tsiv, how do I compile this in windows? Or would you post a windows compilation on github.

[ivanlabrie]

LOL everyone offers alpha/beta testing. Make me laugh.  
Did this happen before with Christian?
Stop this guys, this just makes us look greedy in tsiv's eyes. He will opensource this miner when he thinks it's ready. In the meantime, we still have a lot of others coins to mine.  

EDIT: holy cow. He publishes it 3 seconds before my post. You see? LOL

I'm doing this the Microsoft Way (tm). "If it more or less works, launch it. Maybe fix some huge problems with it sometime next year, if enough people complain long and hard enough. Maybe."

Collect the monero bounty for an open source miner...it was rather decent!
Major props

[Amph]

I'll just... yea, leave this here:

https://github.com/tsiv/ccminer-cryptonight

Do not motherfscking come to me with complaints about lag on Windows, you have been warned

Guess I'll take a look at breaking the one big kernel into smaller pieces that run sequentially, hopefully giving the OS some breathing room. Should at least help with the TDR problem.

Even though I am a AMD miner -  NICE work  

go mine jpc...   there is something new for you there  

small increase on amd for jackpot?

i have seen from 2.1 to 2.5 on 280x, seems good

edit, it's actually much more, like 50%+, very nice

[S_tring]

Could someone share bat config for cryptonight on this new ccMiner?

[leicas]

I'll just... yea, leave this here:

https://github.com/tsiv/ccminer-cryptonight

Do not motherfscking come to me with complaints about lag on Windows, you have been warned

Guess I'll take a look at breaking the one big kernel into smaller pieces that run sequentially, hopefully giving the OS some breathing room. Should at least help with the TDR problem.

Getting 300H/s with -l 5x120 on a 780ti, (compiled with cuda 6.0).

[zelante]

windows 8.1

Code:

[2014-06-24 16:47:02] Using JSON-RPC 2.0
[2014-06-24 16:47:02] Using 40 blocks of 8 threads for cryptonight kernel
[2014-06-24 16:47:02] 2 miner threads started, using 'cryptonight' algorithm.
[2014-06-24 16:47:02] Starting Stratum on stratum+tcp://xmr.coinmine.pl:5555
[2014-06-24 16:47:02] Pool set diff to 200
[2014-06-24 16:47:02] Stratum detected new block
ptxas fatal   : Memory allocation failure
ptxas fatal   : Memory allocation failure
fatal   : Memory allocation failure

[djm34]

windows 8.1

Code:

[2014-06-24 16:47:02] Using JSON-RPC 2.0
[2014-06-24 16:47:02] Using 40 blocks of 8 threads for cryptonight kernel
[2014-06-24 16:47:02] 2 miner threads started, using 'cryptonight' algorithm.
[2014-06-24 16:47:02] Starting Stratum on stratum+tcp://xmr.coinmine.pl:5555
[2014-06-24 16:47:02] Pool set diff to 200
[2014-06-24 16:47:02] Stratum detected new block
ptxas fatal   : Memory allocation failure
ptxas fatal   : Memory allocation failure
fatal   : Memory allocation failure

may-be you should just try first with 1 miner...

[Bombadil]

It's working perfectly fine on my rig ^^"


I have it compiled here for windows: https://mega.co.nz/#!YckmgJpQ!etExS5ELpb309WwSgQcA3WaUPYVwnI4ix9UuWNLr4Yc