[ANN] ccminer 2.3 - opensource - GPL (tpruvot)

[Amph]

GDDR5X GPUs still have issues with compatibility. A 1080 for instance will sometimes get the full 30% speed increase over a 1070, but often times it wont. About half the algos worth mining right now have problems with GDDR5X. You'll get anywhere from 10%-30% (usually around 15%). A 1080ti is no different. It's a shitshow, skein doesn't have problems.

why "half the algo", i only have bad result on ETH and feathercoin, all other algo i'm doing 60-70% more versus a 1070, with my 1080ti and 80-90% on skein/jha

[1713507164]

1713507164

[1713507164]

1713507164

[1713507164]

1713507164

[sp_]

Can you add blake2s/verge and myr-gr/digibyte to yiimp please?

Pallas did a fix in the joincoin wallet to be able to mine to Multiple wallets per machine, perhaps a similar fix can be done in the Verge/digibyte wallets?.

Multiple wallets per machine fix
Fix initialisation hanging on remote tor usage.

https://github.com/pallas1/joincoin/commit/821584e636fed8cc10e43938e0c93f8de7619a32

[pallas]

Can you add blake2s/verge and myr-gr/digibyte to yiimp please?

Pallas did a fix in the joincoin wallet to be able to mine to Multiple wallets per machine, perhaps a similar fix can be done in the Verge/digibyte wallets?.

Multiple wallets per machine fix
Fix initialisation hanging on remote tor usage.

https://github.com/pallas1/joincoin/commit/821584e636fed8cc10e43938e0c93f8de7619a32

On joincoin, after the fix, you could run multiple wallets just by using different conf files with different ports (rpc and p2p); plus you need one "master" tor wallet, and the others who point to it via the -tor option.
Both verge and digibyte probably don't even need the fix.
I think the issue is with coin confusion somewhere in the yiimp code.

[restless]

GDDR5X GPUs still have issues with compatibility. A 1080 for instance will sometimes get the full 30% speed increase over a 1070, but often times it wont. About half the algos worth mining right now have problems with GDDR5X. You'll get anywhere from 10%-30% (usually around 15%). A 1080ti is no different. It's a shitshow, skein doesn't have problems.

These are not issues, but "GDDR5X features"
bandwidth is up, but latency/access for smaller chunks is not, thus algos that do not depend on bandwidth (skein), or can use memory in fully cached chunks scale with cores.
Algos which are critical with latency or non-cached memory access doesn't scale well

[rednoW]

It's a shitshow, skein doesn't have problems.

Why are you talking 'bout skein? )) You were laughing at me when I told you 'bout $10 per gtx1070 some time ago ))

[wacko]

What's up with yiimp skein? Been down for ~ 30 min. Is there any way to specify a failover pool in ccminer?

[bensam1231]

GDDR5X GPUs still have issues with compatibility. A 1080 for instance will sometimes get the full 30% speed increase over a 1070, but often times it wont. About half the algos worth mining right now have problems with GDDR5X. You'll get anywhere from 10%-30% (usually around 15%). A 1080ti is no different. It's a shitshow, skein doesn't have problems.

why "half the algo", i only have bad result on ETH and feathercoin, all other algo i'm doing 60-70% more versus a 1070, with my 1080ti and 80-90% on skein/jha

You should be getting +30% compared to a 1070 with a 1080 and +85% compared to a 1070 with a 1080ti according to cuda counts and pricing. If you're getting 60-70% more then a 1070 with a 1080 you have something misconfigured with your 1070 as it's underperforming. A 1080 and 1080ti will underperform compared to a 1070, but not the opposite direction unless you have something setup wrong. GDDR5 is quite mature, algos have problems with GDDR5X.

As far as what algos are having problems, you've quoted someone of them. I'm not going to tell you about them though.

It's a shitshow, skein doesn't have problems.

Why are you talking 'bout skein? )) You were laughing at me when I told you 'bout $10 per gtx1070 some time ago ))

I never said there weren't coins doing that, I was laughing at you being unable to talk about them because you know they'll get hammered if you do. Remember when I mentioned the 277,000 1070s mining Equihash? Yeah. You have to be a pretty big dumbass if you don't realize what that'll do to any coin you mention, completely taking out of context the whole discussion was about how you can mine mainstream coins with AMD and Nvidia is all niche stuff if you want to make any sort money (which gets hammered immediately) and even then AMD still ends up well off ahead with their mainstream coins.

GDDR5X GPUs still have issues with compatibility. A 1080 for instance will sometimes get the full 30% speed increase over a 1070, but often times it wont. About half the algos worth mining right now have problems with GDDR5X. You'll get anywhere from 10%-30% (usually around 15%). A 1080ti is no different. It's a shitshow, skein doesn't have problems.

These are not issues, but "GDDR5X features"
bandwidth is up, but latency/access for smaller chunks is not, thus algos that do not depend on bandwidth (skein), or can use memory in fully cached chunks scale with cores.
Algos which are critical with latency or non-cached memory access doesn't scale well

What? That's common bogus developer rhetoric. GDDR5X is broken for about half the algos. It needs to be fixed. It's not a feature until it actually does something remotely beneficial. And no it's not a 'oh it's latency and it's broken 4evarrrr' thing, algos need to be tuned to it.

[Vaccinus]

What's up with yiimp skein? Been down for ~ 30 min. Is there any way to specify a failover pool in ccminer?

yeah yiimp is delivering soem problem again for me too, not only skein but bitcore and x17, seems another provider issue? or another ddos, i hope it can be fixed asap, there are not many option to mine skein and x17

[Epsylon3]

i've network issues since 3/4 hours. Trying to understand whats going on

[maxmad_x]

palit gtx 1080 founder edition 700mhs skein @ 140 watt (80%tdp). 5mhs/watt, 62 degrees C with 100% fan.
palit gtx 1080 gamerock        740mhs skein @ 165 watt, 4.4 mhs/watt, 58 degrees C with 75% fan

can you share your settings and system config?
Mine does not do more than 630mh @136w (76% TDP) 65C 70% Fan
System: 6x 1080s gaming x G1820 16gb ddr3 ram

[bensam1231]

i've network issues since 3/4 hours. Trying to understand whats going on

Another attack? XD

Time for some cloudflare.

[_javi_]

how do you name workers with ccminer @ yiimp?? so they get listed in summary below wallet address.

thanks

[scryptr]

how do you name workers with ccminer @ yiimp?? so they get listed in summary below wallet address.

thanks

USE YOUR PASSWORD--

For example, "bilbo, c=VTC" will name your worker "bilbo" and specify VertCoin (VTC) for your payout address.  Your user name, "-u <walletaddress>", is your wallet address.  For some algos there is more than one coin being mined, so specifying the payout coin may be helpful.  It is not always necessary.

This information is in the readme for CCminer.       --scryptr

[rednoW]

palit gtx 1080 founder edition 700mhs skein @ 140 watt (80%tdp). 5mhs/watt, 62 degrees C with 100% fan.
palit gtx 1080 gamerock        740mhs skein @ 165 watt, 4.4 mhs/watt, 58 degrees C with 75% fan

can you share your settings and system config?
Mine does not do more than 630mh @136w (76% TDP) 65C 70% Fan
System: 6x 1080s gaming x G1820 16gb ddr3 ram

It is just an old amd socket am2+ mobo with athlon x2, win7, alexis miner. Then limiting tdp in afterburner and raise clock and mem while it is stable.

[restless]

GDDR5X GPUs still have issues with compatibility. A 1080 for instance will sometimes get the full 30% speed increase over a 1070, but often times it wont. About half the algos worth mining right now have problems with GDDR5X. You'll get anywhere from 10%-30% (usually around 15%). A 1080ti is no different. It's a shitshow, skein doesn't have problems.

These are not issues, but "GDDR5X features"
bandwidth is up, but latency/access for smaller chunks is not, thus algos that do not depend on bandwidth (skein), or can use memory in fully cached chunks scale with cores.
Algos which are critical with latency or non-cached memory access doesn't scale well

What? That's common bogus developer rhetoric. GDDR5X is broken for about half the algos. It needs to be fixed. It's not a feature until it actually does something remotely beneficial. And no it's not a 'oh it's latency and it's broken 4evarrrr' thing, algos need to be tuned to it.

Go read about GDDR5x
It uses same chips as simple gddr5, but with wider 64b per access (32b for gddr5)
Memory latency, access times, its all same.
GDDR5X memory rated 10GBps uses chips which are rated 1.25GBps
GDDR5 memory rated 5GBps uses same, rated 1.25GBps chips.
Bandwidth is up, latency and time to access are same. Think sdram-ddr-ddr2-ddr3-ddr4

Compare 1080 with  "9000Mhz memory" with 1070 using "8000Mhz memory"
1080 uses  1.25GBps chips, 1070 uses chips rated for 2.0GBps. They have way lower latency
Think about how Ryzen fails is some tests, because it s cache latency is much higher

[Barsban]

Please, help to solve this errors. It's --benchmark mode. ccminer crashed or print 'unknown error' at any algorithm. Seems bug related to using of Cuda8.
I try to compile from cuda-8, linux, windows branches with the same effect and errors.
It's on Ubunty 17.10
Other miners with cuda on this machine works fine.

[2017-06-07 18:41:11] GPU #0: unknown error
[2017-06-07 18:41:11] GPU #1: scanhash_blake2s unknown error
[2017-06-07 18:41:12] GPU #0: scanhash_blake2s:433 unknown error
[2017-06-07 18:41:12] GPU #1: ends=7fffffff range=00000000
[2017-06-07 18:41:12] GPU #1: GeForce GTX 1070, 0.00 H/s
[2017-06-07 18:41:13] GPU #0: scanhash_blake2s unknown error
[2017-06-07 18:41:14] GPU #0: ends=00000000 range=00000000
[2017-06-07 18:41:14] GPU #0: GeForce GTX 1070, 0.00 H/s
[2017-06-07 18:41:14] GPU #1: bench_algo_switch_next:120 unknown error
[2017-06-07 18:41:16] GPU #0: bench_algo_switch_next:120 unknown error
[2017-06-07 18:41:19] GPU #1: blake2s hashrate = 0.00 H/s
[2017-06-07 18:41:19] GPU #0: blake2s hashrate = 0.00 H/s
[2017-06-07 18:41:20] Benchmark algo bmw...
[2017-06-07 18:41:20] GPU #0: start=00000000 end=3fffffff range=3fffffff
[2017-06-07 18:41:20] GPU #0: unknown error
[2017-06-07 18:41:20] GPU #0: cuda_check_cpu_init unknown error
[2017-06-07 18:41:21] GPU #1: start=7fffffff end=bffffffe range=3fffffff
[2017-06-07 18:41:21] GPU #1: unknown error
[2017-06-07 18:41:22] GPU #1: cuda_check_cpu_init unknown error
Cuda error in func 'scanhash_bmw' at line 59 : unknown error.
Cuda error in func 'scanhash_bmw' at line 59 : driver shutting down.

[bensam1231]

GDDR5X GPUs still have issues with compatibility. A 1080 for instance will sometimes get the full 30% speed increase over a 1070, but often times it wont. About half the algos worth mining right now have problems with GDDR5X. You'll get anywhere from 10%-30% (usually around 15%). A 1080ti is no different. It's a shitshow, skein doesn't have problems.

These are not issues, but "GDDR5X features"
bandwidth is up, but latency/access for smaller chunks is not, thus algos that do not depend on bandwidth (skein), or can use memory in fully cached chunks scale with cores.
Algos which are critical with latency or non-cached memory access doesn't scale well

What? That's common bogus developer rhetoric. GDDR5X is broken for about half the algos. It needs to be fixed. It's not a feature until it actually does something remotely beneficial. And no it's not a 'oh it's latency and it's broken 4evarrrr' thing, algos need to be tuned to it.

Go read about GDDR5x
It uses same chips as simple gddr5, but with wider 64b per access (32b for gddr5)
Memory latency, access times, its all same.
GDDR5X memory rated 10GBps uses chips which are rated 1.25GBps
GDDR5 memory rated 5GBps uses same, rated 1.25GBps chips.
Bandwidth is up, latency and time to access are same. Think sdram-ddr-ddr2-ddr3-ddr4

Compare 1080 with  "9000Mhz memory" with 1070 using "8000Mhz memory"
1080 uses  1.25GBps chips, 1070 uses chips rated for 2.0GBps. They have way lower latency
Think about how Ryzen fails is some tests, because it s cache latency is much higher

Yeah, still have no idea what sort of a point you're making here. I in no way, shape, or form said that GDDR5X is terrible (it works well for some things, such as gaming), but when it comes to mining it doesn't work well. You essentially made all the points for me. It's terrible in any algo that actually has to use it and while some of them can be fixed (there are algos that utilize memory that don't take a hard hit from using GDDR5X, Equihash was fixed, Lyra2v2 was fixed), there are a decent chunk of them that can't, such as Ethereum.

Calling something a 'feature' when it's broken in the application we're talking about is silly.

[GOLDbarISmine]

what is this nonsense, g5x and g5 are identical

[_javi_]

how do you name workers with ccminer @ yiimp?? so they get listed in summary below wallet address.

thanks

USE YOUR PASSWORD--

For example, "bilbo, c=VTC" will name your worker "bilbo" and specify VertCoin (VTC) for your payout address.  Your user name, "-u <walletaddress>", is your wallet address.  For some algos there is more than one coin being mined, so specifying the payout coin may be helpful.  It is not always necessary.

This information is in the readme for CCminer.       --scryptr

thanks a lot Scryptr.
i checked the readme before posting, but i missed the password as an option for naming workers.
much appreciated!  have a good hashing day!

[pallas]

GDDR5X GPUs still have issues with compatibility. A 1080 for instance will sometimes get the full 30% speed increase over a 1070, but often times it wont. About half the algos worth mining right now have problems with GDDR5X. You'll get anywhere from 10%-30% (usually around 15%). A 1080ti is no different. It's a shitshow, skein doesn't have problems.

These are not issues, but "GDDR5X features"
bandwidth is up, but latency/access for smaller chunks is not, thus algos that do not depend on bandwidth (skein), or can use memory in fully cached chunks scale with cores.
Algos which are critical with latency or non-cached memory access doesn't scale well

What? That's common bogus developer rhetoric. GDDR5X is broken for about half the algos. It needs to be fixed. It's not a feature until it actually does something remotely beneficial. And no it's not a 'oh it's latency and it's broken 4evarrrr' thing, algos need to be tuned to it.

Go read about GDDR5x
It uses same chips as simple gddr5, but with wider 64b per access (32b for gddr5)
Memory latency, access times, its all same.
GDDR5X memory rated 10GBps uses chips which are rated 1.25GBps
GDDR5 memory rated 5GBps uses same, rated 1.25GBps chips.
Bandwidth is up, latency and time to access are same. Think sdram-ddr-ddr2-ddr3-ddr4

Compare 1080 with  "9000Mhz memory" with 1070 using "8000Mhz memory"
1080 uses  1.25GBps chips, 1070 uses chips rated for 2.0GBps. They have way lower latency
Think about how Ryzen fails is some tests, because it s cache latency is much higher

Yeah, still have no idea what sort of a point you're making here. I in no way, shape, or form said that GDDR5X is terrible (it works well for some things, such as gaming), but when it comes to mining it doesn't work well. You essentially made all the points for me. It's terrible in any algo that actually has to use it and while some of them can be fixed (there are algos that utilize memory that don't take a hard hit from using GDDR5X, Equihash was fixed, Lyra2v2 was fixed), there are a decent chunk of them that can't, such as Ethereum.

Calling something a 'feature' when it's broken in the application we're talking about is silly.

equihash and lyra2v2 memory usage is not "fixed" for gddr5x, has just been reduced to almost 0 :-)