z-enemy wins 10-12% Net income of z-enemy miner
My opensource is improving and is now running at the same speed as the enemy miner did a few weeks ago. Every algo has a limit, and the competition can't add 10-15% a week forever.
|
|
|
If see for time, SP_ late with the release of the new miner, z-enemy first, T-Rex second
My miner is not new, and my miner is the fastest opensource by far in the following algos. C11/X16R/X16S/X17
|
|
|
submitted a 40% faster whirlpool80 @github / +6% whirlpool
|
|
|
Submitted a 10% faster fugue implementation @github. Using the same tricks as in my opensource echo implementation with 8 copies of the mixtab table in sharedmem to avoid bank conflicts.
|
|
|
My code is based on ccminer, and alexis78 is one of the contributors. The reason why the file is renamed is that it has been optimized to be faster than in the alexis fork. Alexis improved echo by removing some of the sharemem bank conflicts in AES. He solved this bymoving some of the tables to the global memory (level1 cache). I increased the shared mem buffer by having several copies of the the aes table and removed all of the sharemem conflicts. this resulted in a +30% faster echo. The alexis echo function is based on my work back in 2015. Back then I precualculated the P[] table to save some AES rounds among other improvements.
|
|
|
What coins did you mine to RVN wallet? Have you checked if those price was stable? I mean only reason for a price drop is coin prices on exchange
I mine on the x16r port without specifying any coin, but the payout is in RVN. I use c=RVN in the password. the test is still running. Today I see that the balance dropped after the exchange has taken place. (the blue line in the circle.) When I mine with c=RVN, shouldn't the blue line always grow? ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FLnlKaLZ.png&t=663&c=igk5WVW9p11JOA)
|
|
|
Z270 - 5 x 1060 2 x 1070 - BSODs too often
Check the power usage. reduce the tdp limit of the cards in msi afterburner or similar tool. You can also try to reduce the intensity with the -i parameter. -i 21 is a popular choice.
|
|
|
I have been testing your x16r pool with payouts in raven. c=RVN in the password claimed 24hour profit by the pool: 0.0011722 BTC/GHASH actual profit(24hours): 0,0079696 BTC/GHASH (yesterdays price of 0.00000320btc/raven) actual profit(24hours): 0,00737188 BTC/GHASH (todays price of 0.00000294btc/raven) From the graph you can see that the balance sometimes drops. So hashing for 8 hours in two periods didn't increase the balance even if new blocks where found. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Fo0d1LZh.png&t=663&c=tJ7b5SkG004ZVQ) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F1lpI4Mu.png&t=663&c=-B1CNrZMUwCTrQ)
|
|
|
no, but I will release a faster phi2 sp-mod private soon. (0.05btc)
|
|
|
My miner isn't performing good when the latency on the pool is high. This is a known issue from ccminer 2.2.4 & cminer 1.0 alexis. Job not found rejected shares. etc,. The fee miners have improved the stratum code, and gained few percent more pool shares with a lower hashrate (gpu speed)..
These issues are fixed in spmod-git #10
|
|
|
X16r/X16s/C11 Spmod-git #10 has been released - Fixed double nonce submission in simd and some other algos. (faster x16r/x16s) - Improved the the poolside hashrate when mining on high intensity or/and low difficulty. (removed double work after a solution had been found) - Reduced the pool network traffic by increasing the workload to the gpu to scan the whole 32bit nonce range. - Reduced rejected shares on the pool. - Added pool latency and blocks found to the miner output This miner is free without any fee. Linux/Windows cuda 9.2 binary: https://github.com/sp-hash/suprminer/releasessource: https://github.com/sp-hash/suprminer/commits/master
|
|
|
and you still try to portrait yourself as open source dev??
What do you call this? https://github.com/sp-hash/suprminer/commits/master70 opensource commits done by me since 9th of may 2018. Mostly x16r improvements, but with some copy and paste skills you should be able to beat the alexis 1.0 in all his algos. The competition compare and use my opensource work so they can get a faster hashrate.
|
|
|
Sure you paid .05 btc for something that is now slower and free. Relax. You'll survive.
My mods come with free updates. If the competition improves, I release a new faster binary.
|
|
|
Cuda 9.2 perform bether with more registers. You need launchbounds on youur kernels. In my opensource i have changed the register usage in the project file (visual studio). These adjustments are not added to the linux makefile.
|
|
|
and these are the words of the developer who has studied all the works of SP and other miners
I have 1300 commits to the ccminer opensource project at github(2014-2018). What have you done for the community besides throwing shit in my thread?. The stratum code in ccminer need some work. My miner isn't performing good when the latency on the pool is high. This is a known issue from ccminer 2.2.4 & cminer 1.0 alexis. Job not found rejected shares. etc,. The fee miners have improved the stratum code, and gained few percent more pool shares with a lower hashrate (gpu speed).. Points to work on: 1. Never disconnect to the pool. 2. Reduce the sleep time 3. Cleanup of the blocking thread code. Then you compile with cude 9.1, rewrite all the output to the command line, add a fee, make a stupid name and publish the new "faster" miner with my opensouce gpu kernel code inside... You might need to add a couple of puppy accounts here on bitcointalk, make a discord channel, buy some positive reviews, and then you are in business.. May the fee be with you. :-)
|
|
|
A raw estimate can be made by comparing number of cuda cores (only for low memory usage algos). Power usage (at same clock and number of cuda cores) should be 10-15% less.
12nm production, vs 14nm for the pascal. Less heat and higher clocks should be possible. X16r/x16s/X17/C11 etc. should be around 50% faster than the pacal cards.. My guess 2080ti +50%
|
|
|
@sp_ code is not compiling due to an error
I have submitted a fix @ github
|
|
|
|