[ANN]pledge for the release of 100% faster cuda 7.5 nvidia miner for neoscrypt

[Grim]

@ djm

well lyra2v2 is quite hot now

Considering 750ti is useless mining eth it is THE algo for 750ti rigs.

I bet you would reach ~2 btc (without nicehash), moreover lyra2v2 has more coins with higher cap compared to neoscrypt.

[sp_]

But how fast is it?

[djm34]

But how fast is it?

quite frankly, I don't remember... I haven't run it in months, but as I said, I don't plan to release it at the moment.

[djm34]

@ djm

well lyra2v2 is quite hot now

Considering 750ti is useless mining eth it is THE algo for 750ti rigs.

I bet you would reach ~2 btc (without nicehash), moreover lyra2v2 has more coins with higher cap compared to neoscrypt.

well I don't know... actually I could set an address and release whenever I feel there is enough  
(you might have to wait quite some time...) Do I sound like a scam ? 

[sp_]

I have only added 500KHASH on the 980 (sp-mod 61-git) Which algos did you rewrite? And will you make it public?

rewrote lyra2 code:

Good job.
I guess the new kernal is using more power?

yes, the 980 runs at 110% tpd and the 750ti close to 95% (on my gainward stock).
Honestly I will try to backport (if possible... not entirely obvious though, the new kernel relies on warp shuffle technique) some of the change to amd before releasing it, I don't want to create more imbalance...

[sp_]

I think you had another pic as well with 6.2 mhash on the 750ti but can't find it.

[Grim]

@ djm

well lyra2v2 is quite hot now

Considering 750ti is useless mining eth it is THE algo for 750ti rigs.

I bet you would reach ~2 btc (without nicehash), moreover lyra2v2 has more coins with higher cap compared to neoscrypt.

well I don't know... actually I could set an address and release whenever I feel there is enough  
(you might have to wait quite some time...) Do I sound like a scam ? 

nope, that's exactly how I feel you should do it


and actions speak louder than words:

Status: 0/unconfirmed
Date: 27.01.2016 13:58
To: djm34 main donation 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze
Debit: -0.15000000 BTC
Transaction fee: -0.00002906 BTC
Net amount: -0.15002906 BTC
Transaction ID: aa4743f6733b18f0f1448faf0c479634a5663071ef1adb622936129af4e23d87-000



I hope you reimburse me in case you don't release it in the next few weeks/months...  

[sp_]

My current private mod mines lyra2v2 at 5,5MHASH on the 750ti with max overclock.

And 5050 on standard clocks. (EVGA SC 750ti)

[djm34]

@ djm

well lyra2v2 is quite hot now

Considering 750ti is useless mining eth it is THE algo for 750ti rigs.

I bet you would reach ~2 btc (without nicehash), moreover lyra2v2 has more coins with higher cap compared to neoscrypt.

well I don't know... actually I could set an address and release whenever I feel there is enough  
(you might have to wait quite some time...) Do I sound like a scam ?  

nope, that's exactly how I feel you should do it


and actions speak louder than words:

Status: 0/unconfirmed
Date: 27.01.2016 13:58
To: djm34 main donation 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze
Debit: -0.15000000 BTC
Transaction fee: -0.00002906 BTC
Net amount: -0.15002906 BTC
Transaction ID: aa4743f6733b18f0f1448faf0c479634a5663071ef1adb622936129af4e23d87-000



I hope you reimburse me in case you don't release it in the next few weeks/months...  

thanks a lot, but please wait that I set a new address (also as I said I have no plan to release it at the moment)

[djm34]

My current private mod mines lyra2v2 at 5,5MHASH on the 750ti with max overclock.

I'll ask some of my contact to check that

[sp_]

My current private mod mines lyra2v2 at 5,5MHASH on the 750ti with max overclock.

I'll ask some of my contact to check that

Depends on the cards and what memory they use.. Your neoscrypt is only doing 170-180khash on some cards and 200khash on others even if the clock setting is the same.
Could be the windows7 vs windows 8.1 problem. Or samsung/elpida/hynix memory latency differences.

[djm34]

My current private mod mines lyra2v2 at 5,5MHASH on the 750ti with max overclock.

I'll ask some of my contact to check that

Depends on the cards and what memory they use.. Your neoscrypt is only doing 170-180khash on some cards and 200khash on others even if the clock setting is the same.
Could be the windows7 vs windows 8.1 problem. Or samsung/elpida/hynix memory latency differences.

most likely related to the OS (easy to check with the spreadsheet)

[Grim]

thanks a lot, but please wait that I set a new address (also as I said I have no plan to release it at the moment)

just forward it to your new address if you ever go all the way ...

[Pivlus]

For those interested in the OS issue, I just booted off a Win 8.1 x64 drive, same rig, same settings, hash went from previous 720 kH/s (Win 10 x64) to 837 kH/s. Using ccminer-djm34-neoscrypt-65.

[Eliovp]

For those interested in the OS issue, I just booted off a Win 8.1 x64 drive, same rig, same settings, hash went from previous 720 kH/s (Win 10 x64) to 837 kH/s. Using ccminer-djm34-neoscrypt-65.

Now try Windows 10 Pro 64Bit. I believe you will go even faster. I did

[Pivlus]

For those interested in the OS issue, I just booted off a Win 8.1 x64 drive, same rig, same settings, hash went from previous 720 kH/s (Win 10 x64) to 837 kH/s. Using ccminer-djm34-neoscrypt-65.

Now try Windows 10 Pro 64Bit. I believe you will go even faster. I did

In fact, as I posted earlier, my experience was quite the opposite. I was on Win 10 Pro x64 (as posted in the Mining Hardware Comparison chart) and going back to Win 8.1 increased my hashrate. Later on I might try to revert to Win 7, unless someone in this thread has already tested and found no difference between Win 8.1 (Pro x64) and Win 7 (Ultimate x64).

[Eliovp]

For those interested in the OS issue, I just booted off a Win 8.1 x64 drive, same rig, same settings, hash went from previous 720 kH/s (Win 10 x64) to 837 kH/s. Using ccminer-djm34-neoscrypt-65.

Now try Windows 10 Pro 64Bit. I believe you will go even faster. I did

In fact, as I posted earlier, my experience was quite the opposite. I was on Win 10 Pro x64 (as posted in the Mining Hardware Comparison chart) and going back to Win 8.1 increased my hashrate. Later on I might try to revert to Win 7, unless someone in this thread has already tested and found no difference between Win 8.1 (Pro x64) and Win 7 (Ultimate x64).

Oh, that's weird. But good to know none the less. thank you for your feedback and especially for submitting @ mininghwcomparison! Greatly appreciated!!

[djm34]

For those interested in the OS issue, I just booted off a Win 8.1 x64 drive, same rig, same settings, hash went from previous 720 kH/s (Win 10 x64) to 837 kH/s. Using ccminer-djm34-neoscrypt-65.

Now try Windows 10 Pro 64Bit. I believe you will go even faster. I did

from the discussion we had on irc, I understood you were running only amd cards 

from my experience but that was right after the launch of win 10 (first install 2 or 3 days after the official win10 launch; second and last, was a month later with the release of new nvidia drivers) the performance on lyra and neoscrypt was rather bad (and gaming was laggy as well) and I preferred to go back to win 8.1. Might try again (in principle you can revert during the first month...  so far I reverted after 4 or 5 hours each time...).
However there is a cuda win10 version, I never tried it, so may-be it requires to recompile with it (?), so if someone has win10 and knows to compile, he can try that: download the cuda win10 edition and recompile with it and see what will happen.

[Eliovp]

For those interested in the OS issue, I just booted off a Win 8.1 x64 drive, same rig, same settings, hash went from previous 720 kH/s (Win 10 x64) to 837 kH/s. Using ccminer-djm34-neoscrypt-65.

Now try Windows 10 Pro 64Bit. I believe you will go even faster. I did

from the discussion we had on irc, I understood you were running only amd cards 

from my experience but that was right after the launch of win 10 (first install 2 or 3 days after the official win10 launch; second and last, was a month later with the release of new nvidia drivers) the performance on lyra and neoscrypt was rather bad (and gaming was laggy as well) and I preferred to go back to win 8.1. Might try again (in principle you can revert during the first month...  so far I reverted after 4 or 5 hours each time...).
However there is a cuda win10 version, I never tried it, so may-be it requires to recompile with it (?), so if someone has win10 and knows to compile, he can try that: download the cuda win10 edition and recompile with it and see what will happen.

True true. Was mainly referring to the fact that mining in general went a bit faster when i switched to win10. I assumed that would have been the same for Nvidia based cards.

But that seems not to be true. 

[djm34]

For those interested in the OS issue, I just booted off a Win 8.1 x64 drive, same rig, same settings, hash went from previous 720 kH/s (Win 10 x64) to 837 kH/s. Using ccminer-djm34-neoscrypt-65.

Now try Windows 10 Pro 64Bit. I believe you will go even faster. I did

from the discussion we had on irc, I understood you were running only amd cards 

from my experience but that was right after the launch of win 10 (first install 2 or 3 days after the official win10 launch; second and last, was a month later with the release of new nvidia drivers) the performance on lyra and neoscrypt was rather bad (and gaming was laggy as well) and I preferred to go back to win 8.1. Might try again (in principle you can revert during the first month...  so far I reverted after 4 or 5 hours each time...).
However there is a cuda win10 version, I never tried it, so may-be it requires to recompile with it (?), so if someone has win10 and knows to compile, he can try that: download the cuda win10 edition and recompile with it and see what will happen.

True true. Was mainly referring to the fact that mining in general went a bit faster when i switched to win10. I assumed that would have been the same for Nvidia based cards.

But that seems not to be true. 

actually memory hard algo speed went a bit down, which is in my opinion linked to the memory management in win10 (or the wdm windows driver model)