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

[7854587]

GTS 450 cannot use 1.2
Requests the configuration?

[hero18688]

My 750ti got around 1500 k/h .How do you make it 1600k/h

[S_tring]

to be honest I am not sure this is entirely a good idea.
Beside the fact, we will end up with some big stuff, Cudaminer and ccminer are two different softwares.  
I don't really see the point in putting them together. Blake512 can be moved (and I was thinking to do it, however it isn't on my top priority list) to ccminer for the rest this is less obvious.
It would be like merging ms words and powerpoint. (sure it could work, but it isn't that useful)

Yes I agree and that is also what makes it VERY DIFFICULT is that the two programs are similar but different also.  But if all the algos can be moved into one EXE if possible (still not sure it can be done) why not try?  The more algos we can support in one EXE (program) the easier it will be for people to use nVidia hardware and should make support a lot easier.  Would you not agree?  This is one of the biggest issue with AMD hardware IMHO at the moment (you need multiple different programs for all the algos).

This would be much easier if it were done by Christian who is ultimately familiar with both programs!!!  If he were to do it then no one would question it but only welcome it (myself included!).

I know we right now support both Windows and Linux.  If we were to diverge (not sure it's a good idea) from this I could build DLL files for each algo which would make compiling and integration of additional algos so much easier from a windows standpoint.  But I resist for now.

But I  respect your opinion djm34. Could you elaborate on why you think this might not be a good idea? (from an end user standpoint and not from a dev standpoint)
IMHO I would think 99% of the users would like one program regardless of what hell we as devs might need to go through to make this one program!

BTW, part of what I'm trying to do is make it easier for devs like yourself, tsiv and Christian.  You can concentrate on just the unique algos you want to work on and for now and I'll work on integrating it into a "master" framework.  This way each of you only has to work/worry about your own code.  I'll try and take care of the rest.  Maybe after I publish the "master" nvMiner code others can also help with integration.

Thanks,
Carlo

PS Any non devs want to comment on what you'd like?

I don't see a problem having 2 miner. Anyway , cuda is sort of like "old miner" and cc is like "new miner". What's on cuda will slowly phase out by year end. It's like SHA got phase out from GPU. I don't think its a good idea to waste your precious time on old stuff. If u spend equal amount of time on "new" development (e.g improving base algo hashrate. Like improving groetl pretty much improve all algo hashrate) , that is time well spend IMO.  

+1

[DemosMirak]

GTS 450 cannot use 1.2
Requests the configuration?

That card is a CUDA 2.1 card, you will need the CUDA 2.0 versions of the miner, which can be found at http://cudamining.cc/url/releases.

[PVmining]

I don't see a problem having 2 miner.

+1
I see no problem two have two miners... 
Different miner developments for linux & windows would be a bad idea.

[ilovecudacompute]

I want to thank every epic person involved in this epic thread ...the developers/programmers...the testers...the people who post binaries...
This thread is helping all of us mine and why not make some profit  

Keep up the god's work  


PS Thanks djm for new x15....i jump from 1.3 to 1.5MH 

[yellowduck2]

"new" algo whirlpool.

https://bitcointalk.org/index.php?topic=679134.new#new

This "new" algo was in x15 ? Let's make this coin Nvidia coin 

[djm34]

"new" algo whirlpool.

https://bitcointalk.org/index.php?topic=679134.new#new

This "new" algo was in x15 ? Let's make this coin Nvidia coin 

This is certainly the worst of all the algo for nvidia... why people are making coin based on algo which didn't even made to the final of the nist competition ?
(actually if the bounty can replace the instamine why not...  )

[cbuchner1]

whirlpool can be bitsliced, I think and it may also be possible to split its state across several threads, like our quad groestl implementation does.

[yellowduck2]

whirlpool can be bitsliced, I think and it may also be possible to split its state across several threads, like our quad groestl implementation does.

which means x15 hashrate can be further improved ?

[djm34]

whirlpool can be bitsliced, I think and it may also be possible to split its state across several threads, like our quad groestl implementation does.

which means x15 hashrate can be further improved ?

I suppose so...
regarding whirlpool coin, it will require some extra coding in both amd and nvidia code... so it could really be cpu only for a little while... ( wonder why they didn't do a ninja launch... at least I can work on my wallet...)

[barabeku]

whirlpool can be bitsliced, I think and it may also be possible to split its state across several threads, like our quad groestl implementation does.

which means x15 hashrate can be further improved ?

I suppose so...
regarding whirlpool coin, it will require some extra coding in both amd and nvidia code... so it could really be cpu only for a little while... ( wonder why they didn't do a ninja launch... at least I can work on my wallet...)

Why we can't just remove other algos based on x15 miner?

[Amph]

whirlpool can be bitsliced, I think and it may also be possible to split its state across several threads, like our quad groestl implementation does.

which means x15 hashrate can be further improved ?

I suppose so...
regarding whirlpool coin, it will require some extra coding in both amd and nvidia code... so it could really be cpu only for a little while... ( wonder why they didn't do a ninja launch... at least I can work on my wallet...)

Why we can't just remove other algos based on x15 miner?

the first algo is the one that give problem, if this was x2 with first algo being the one in x15/x14/x13, then just remove everything else and you are done, but this isn't the case

for qubit luffa512 was using some extra code, which i found in blake512 also, both are first algo, i suppose that for whirlpool you need some additional extra code compared to those two...

[bathrobehero]

FreshCoin is a revolutionary Fresh PoW coin featuring a new FRESH mining algorithm.  This new algorithm consumes 15% to 20% less energy compared to x11 / x13 / 15. The FRESH algorithm cherry picked and combined the most low energy hashing algorithms (SHAVITE, SIMD & ECHO) which results in the most ENERGY efficient hashing solution available. The combination of 5 rounds of multiple algorithms stand for high security and will keep ASIC miners away.

This looks nice! And there's a bounty for ccminer.

https://bitcointalk.org/index.php?topic=670939.0

[RavenXBR]

to be honest I am not sure this is entirely a good idea.
Beside the fact, we will end up with some big stuff, Cudaminer and ccminer are two different softwares.  
I don't really see the point in putting them together. Blake512 can be moved (and I was thinking to do it, however it isn't on my top priority list) to ccminer for the rest this is less obvious.
It would be like merging ms words and powerpoint. (sure it could work, but it isn't that useful)

Yes I agree and that is also what makes it VERY DIFFICULT is that the two programs are similar but different also.  But if all the algos can be moved into one EXE if possible (still not sure it can be done) why not try?  The more algos we can support in one EXE (program) the easier it will be for people to use nVidia hardware and should make support a lot easier.  Would you not agree?  This is one of the biggest issue with AMD hardware IMHO at the moment (you need multiple different programs for all the algos).

This would be much easier if it were done by Christian who is ultimately familiar with both programs!!!  If he were to do it then no one would question it but only welcome it (myself included!).

I know we right now support both Windows and Linux.  If we were to diverge (not sure it's a good idea) from this I could build DLL files for each algo which would make compiling and integration of additional algos so much easier from a windows standpoint.  But I resist for now.

But I  respect your opinion djm34. Could you elaborate on why you think this might not be a good idea? (from an end user standpoint and not from a dev standpoint)
IMHO I would think 99% of the users would like one program regardless of what hell we as devs might need to go through to make this one program!

BTW, part of what I'm trying to do is make it easier for devs like yourself, tsiv and Christian.  You can concentrate on just the unique algos you want to work on and for now and I'll work on integrating it into a "master" framework.  This way each of you only has to work/worry about your own code.  I'll try and take care of the rest.  Maybe after I publish the "master" nvMiner code others can also help with integration.

Thanks,
Carlo

PS Any non devs want to comment on what you'd like?

Besides Scrypt related coins are "worthless" to GPU mine now, I do agree as the user point of view.

I also would like to point how Nvidia mining community is mature discussing opposite opinions in a polite/constructive way instead of flame and brute force.
Congratz to all devs and community at all. 

[barabeku]

whirlpool can be bitsliced, I think and it may also be possible to split its state across several threads, like our quad groestl implementation does.

which means x15 hashrate can be further improved ?

I suppose so...
regarding whirlpool coin, it will require some extra coding in both amd and nvidia code... so it could really be cpu only for a little while... ( wonder why they didn't do a ninja launch... at least I can work on my wallet...)

Why we can't just remove other algos based on x15 miner?

the first algo is the one that give problem, if this was x2 with first algo being the one in x15/x14/x13, then just remove everything else and you are done, but this isn't the case

for qubit luffa512 was using some extra code, which i found in blake512 also, both are first algo, i suppose that for whirlpool you need some additional extra code compared to those two...

Ok, so i need to setgenerate at first run. I'll be ready with 10 instance with 8 cores each.

[RavenXBR]

to be honest I am not sure this is entirely a good idea.
Beside the fact, we will end up with some big stuff, Cudaminer and ccminer are two different softwares.  
I don't really see the point in putting them together. Blake512 can be moved (and I was thinking to do it, however it isn't on my top priority list) to ccminer for the rest this is less obvious.
It would be like merging ms words and powerpoint. (sure it could work, but it isn't that useful)

Yes I agree and that is also what makes it VERY DIFFICULT is that the two programs are similar but different also.  But if all the algos can be moved into one EXE if possible (still not sure it can be done) why not try?  The more algos we can support in one EXE (program) the easier it will be for people to use nVidia hardware and should make support a lot easier.  Would you not agree?  This is one of the biggest issue with AMD hardware IMHO at the moment (you need multiple different programs for all the algos).

This would be much easier if it were done by Christian who is ultimately familiar with both programs!!!  If he were to do it then no one would question it but only welcome it (myself included!).

I know we right now support both Windows and Linux.  If we were to diverge (not sure it's a good idea) from this I could build DLL files for each algo which would make compiling and integration of additional algos so much easier from a windows standpoint.  But I resist for now.

But I  respect your opinion djm34. Could you elaborate on why you think this might not be a good idea? (from an end user standpoint and not from a dev standpoint)
IMHO I would think 99% of the users would like one program regardless of what hell we as devs might need to go through to make this one program!

BTW, part of what I'm trying to do is make it easier for devs like yourself, tsiv and Christian.  You can concentrate on just the unique algos you want to work on and for now and I'll work on integrating it into a "master" framework.  This way each of you only has to work/worry about your own code.  I'll try and take care of the rest.  Maybe after I publish the "master" nvMiner code others can also help with integration.

Thanks,
Carlo

PS Any non devs want to comment on what you'd like?

I don't see a problem having 2 miner. Anyway , cuda is sort of like "old miner" and cc is like "new miner". What's on cuda will slowly phase out by year end. It's like SHA got phase out from GPU. I don't think its a good idea to waste your precious time on old stuff. If u spend equal amount of time on "new" development (e.g improving base algo hashrate. Like improving groetl pretty much improve all algo hashrate) , that is time well spend IMO.  

I shall agree with that.
To have a single miner would be awesome, but improving "lucrative" algos and new features should be priority.

 

[djm34]

FreshCoin is a revolutionary Fresh PoW coin featuring a new FRESH mining algorithm.  This new algorithm consumes 15% to 20% less energy compared to x11 / x13 / 15. The FRESH algorithm cherry picked and combined the most low energy hashing algorithms (SHAVITE, SIMD & ECHO) which results in the most ENERGY efficient hashing solution available. The combination of 5 rounds of multiple algorithms stand for high security and will keep ASIC miners away.

This looks nice! And there's a bounty for ccminer.

https://bitcointalk.org/index.php?topic=670939.0

the bounty is pretty small (compared to the block reward actually...   )
The code is already written, I will upload to  github, once I hear from the coin dev, to be sure it works before uploading anything...)

[RavenXBR]

My 750ti got around 1500 k/h .How do you make it 1600k/h

I can make 1550~1575K each card (sometimes it hits 1600K) on a 4 GPU rig (ribbon non-powered risers) with +135 GPU and +400 MEM OC.
Still tweaking MEM OC... last night +450 crashed ccminer while I was sleeping after almost 24h running straight with no problem.

- GPU: Gigabyte GV-N75TOC-2GI
- OC SW: EVGA Precision X

 

[yellowduck2]

FreshCoin is a revolutionary Fresh PoW coin featuring a new FRESH mining algorithm.  This new algorithm consumes 15% to 20% less energy compared to x11 / x13 / 15. The FRESH algorithm cherry picked and combined the most low energy hashing algorithms (SHAVITE, SIMD & ECHO) which results in the most ENERGY efficient hashing solution available. The combination of 5 rounds of multiple algorithms stand for high security and will keep ASIC miners away.

This looks nice! And there's a bounty for ccminer.

https://bitcointalk.org/index.php?topic=670939.0

the bounty is pretty small (compared to the block reward actually...   )
The code is already written, I will upload to  github, once I hear from the coin dev, to be sure it works before uploading anything...)

Please do not upgrade AMD miner hashrate. Talkcoin was good for NVIDIA until "someone" double AMD hashrate. If really need to improve AMD hashrate , 1 month after launch will be ideal. AMD miner is like ASIC. Updating ASIC hashrate is generally a bad idea. NVIDIA need a new home. Perhaps this will be a NVIDIA coin ?