Here is some info I got, but still testing.... check out the Reddit post. Just sharing my info, I welcome insight, coaching and recommendations to get the best info for the community. I done some more testing, per other miners request on specific algos, and below the link to reddit is today's testing. https://www.reddit.com/r/gpumining/comments/9ixng5/rtx_2080_mining_hashrateperformance/I will continue to update the threads as soon as I can. Thank you, SerpentXSF CMVJAX X16r - 30mh X16s - 14mh X17 - 14mh X16 algos should be benched for long time. But +/- they should be equal x17. |
|
|
|
It seems we have a bug here with multi GPU. Does this difference also exist when you use olets say only 2 GPU in one instance (--devices 0,1)
It seems to be so Start Mining...
New job received: e24b
Average speed (30s): 22.9 sol/s | 22.3 sol/s Total: 45.3 sol/s
New job received: e24c
Average speed (30s): 20.5 sol/s | 21.9 sol/s Total: 42.4 sol/s |
|
|
|
running from 21-23 sols per card which is equivalent to a gtx 1060 on ewbf 0.5
Are you joking? 1060 on PL60 makes 26-27sol/s on not the best 1060. |
|
|
|
Got a 8*1060 rig ewbf makes 210-240sol/s depending on PL(60-90)
Your miner makes only 116-130sol/s also depending on PL(60-90).
But with 5*1080 it is closer:
ewbf - 240sol/s
lol ~ 200sol/s
Ah, thats interesting. I have seen that with MNX in the past that the 1060 series reacts different to code then 1080. Good to know that this is the case here. Can you do me a favor and delete the 144_5_NV.bin file from.the kernel dir and see again what happens? The Nvidias should then load the AMD kernel and I would like to know if that works better for the 1060 cards. Thx for reporting! Memo to myself: need a 1060 for testing... No - the same +/- Kernel file not found: ./kernels/144_5/144_5_NV.bin
Connecting to pool...
Connected to equihash144.mine.zergpool.com:2146
Subscribed to stratum server
New target received: 0010000000000000
New job received: e2ef
Authorized worker: t1WqEZjk3ytvsmDYCKPW5VBDpPDAS2ixGBe
Start Mining...
New job received: e2f0
New job received: e2f1
New job received: e2f2
Average speed (30s): 20.2 sol/s | 12.3 sol/s | 13.2 sol/s | 12.7 sol/s | 12.6 sol/s | 12.3 sol/s | 14.8 sol/s | 13.1 sol/s Total: 111.4 sol/s
Submitting share
Share accepted
New job received: e2f3
Average speed (30s): 19.9 sol/s | 12.6 sol/s | 15.5 sol/s | 14.3 sol/s | 11.9 sol/s | 14.2 sol/s | 14.3 sol/s | 12.7 sol/s Total: 115.4 sol/s
It would be also more informative to add time stamp. And those ~20sol/s on GPU0 against all other is also seen on 1080 (less difference but still exist). GPU0 is faster in your miner. But GPUs are the same. Immediately after your miner - ewbf. GPU's vary around the same hashrate: 19:45:11 INFO: GPU1 Accepted share 110ms [A:1, R:0]
19:45:17 INFO: Detected new work: dd85 [ZelProof]
19:45:23 INFO: GPU3 Accepted share 110ms [A:1, R:0]
19:45:28 Temp: GPU0: 39C GPU1: 39C GPU2: 38C GPU3: 37C GPU4: 39C GPU5: 37C GPU6: 37C GPU7: 42C
19:45:28 GPU0: 27 Sol/s GPU1: 26 Sol/s GPU2: 25 Sol/s GPU3: 28 Sol/s GPU4: 25 Sol/s GPU5: 26 Sol/s GPU6: 24 Sol/s GPU7: 25 Sol/s
19:45:28 Total speed: 206 Sol/s
19:45:41 INFO: GPU7 Accepted share 110ms [A:1, R:0]
19:45:52 INFO: GPU5 Accepted share 123ms [A:1, R:0]
19:46:02 Temp: GPU0: 42C GPU1: 43C GPU2: 41C GPU3: 41C GPU4: 42C GPU5: 40C GPU6: 40C GPU7: 44C
19:46:02 GPU0: 25 Sol/s GPU1: 24 Sol/s GPU2: 26 Sol/s GPU3: 26 Sol/s GPU4: 24 Sol/s GPU5: 28 Sol/s GPU6: 25 Sol/s GPU7: 27 Sol/s
19:46:02 Total speed: 205 Sol/s
19:46:09 INFO: GPU5 Accepted share 110ms [A:2, R:0]
19:46:11 INFO: GPU2 Accepted share 109ms [A:1, R:0]
19:46:12 INFO: Detected new work: dd86 [ZelProof]
19:46:13 INFO: GPU2 Accepted share 110ms [A:2, R:0]
19:46:36 Temp: GPU0: 44C GPU1: 45C GPU2: 44C GPU3: 43C GPU4: 44C GPU5: 43C GPU6: 42C GPU7: 46C
19:46:36 GPU0: 26 Sol/s GPU1: 25 Sol/s GPU2: 25 Sol/s GPU3: 28 Sol/s GPU4: 27 Sol/s GPU5: 26 Sol/s GPU6: 27 Sol/s GPU7: 26 Sol/s
19:46:36 Total speed: 210 Sol/s |
|
|
|
For equihash 144,5 performance has been improved, at
least for gtx 1080 on which Funakoshi-Miner is considerably
faster than EWBF. I haven't optimized for 1060 yet.
For equihash 200,9 Funakoshi-Miner is much faster on all devices.
Already told you that your miner is not faster then ewbf. It was considerably slower. Now it it closer but still a little bit behind. On 5*1080 ewbf ~ 245-250 your ~ 233-238 Good progress anyway. |
|
|
|
|
Got a 8*1060 rig ewbf makes 210-240sol/s depending on PL(60-90)
Your miner makes only 116-130sol/s also depending on PL(60-90).
But with 5*1080 it is closer:
ewbf - 240sol/s
lol ~ 200sol/s
|
|
|
|
There is a problem with miner autostart on a rig without monitor. At 19:50 I logged in by RDP and miner moved on. But it was hanging for an hour after reboot doing nothing. CastXMR work on the same rig without such problem. Total pools: 3
Please wait...
Cryptonight StelliteV4 mode enabled
[2018-09-20 18:42:01] Heating up system, please wait...
[2018-09-20 19:50:51] Loading compiled kernel for DEVICE BUS ID 7 ...
[2018-09-20 19:50:53] Loading compiled kernel for DEVICE BUS ID 7 ...
[2018-09-20 19:50:54] Loading compiled kernel for DEVICE BUS ID 17 ... |
|
|
|
I have just seen this news on twitter page - the link: https://twitter.com/marpme_/status/1041671148025597953Is this KMD working on ledger or they are developing for XVG to be used on ledger ? Perhaps we are ready to join this big party after officially announcement released out . looks like XVG being tested on ledger, not KMD.  not sure if this is big news enough to be a big impact tho. but it's nice to have it on ledger as well. KMD is working on ledger for at least a year. |
|
|
|
I tested bsod a few weeks ago. The opensource miners (sp-mod) seems to be finding more blocks. The fee miners have optimized the stratum code and seem to be stealing from the other miners.
The main thief in cryptomining sphere is accusing others in stealing? From now on introducing new idioma - "doing an sp_" - stealing others code and selling private miners with miserable knowledge in programming  |
|
|
|
hello,
Is it possible to mine X16R solo on that miner?
Not with the opensource, but you can try https://bsod.pw with -p solo in the password. 0.03334BTC / GHASH with solomining. 3-4 times more profitable than mining on the other yiimp clone pools. Did a short test with 5GHASH and got 6 blocks, around 30000 raven in 24 hours with the sp-mod.. pretty good. Luck is luck, but bsod API reports "actual_last24h_solo":0.00827. P.S. With t-rex/z-enemy you could get 7 blocks. |
|
|
|
100 is too smal quantity to be lucky enough for getting stake. I would suggest to buy/mine more coins to have a POS rewards on stable basis. As example, here is my recent stakes with 550 coins in "game"  550 coins staking continuously and get around 3 times of staking rewards (0.8 LUX for each time). It also means that each day 550 staked coins can return nearly 2.4 coins as staking rewards. thats odd I've got 540 coins staking 24/7 and I get one stake every 4 days on average  I have 200 coins and haven't ever get any reward while wallet was constantly updated and running 24/7 with staking enabled. There is definetly some margin. Below that margin no stakng at all. |
|
|
|
Let's say I have a raven miner that is 20% faster than enemy 1.20. Then I deploy this miner on my xxx xxx 1080ti cards and solomine raven. Your profit ill be shreaded, and you will move to another more profitable coin. (ethereum)
Now we know your wet sleazy dreams Dreams, dreams, dreams. P.S. t-rex already released 0.6.8 version So stop jerking on your fantasies - you should steal faster, faster .... much faster. Ooops - it requires more knowledge than to adapt alexis98 code to new algos |
|
|
|
CUfunction ASM_SIMD = NULL;
// if (LoadPtxKernel("Enemy_120_simd_32_52.ptx", &ASM_SIMD) != CUDA_SUCCESS)
if (LoadPtxKernel("cuda_x11_simd512.compute_52.ptx", &ASM_SIMD) != CUDA_SUCCESS)
{
exit(EXIT_FAILURE);
}
Competition is good for the hashrate. My fork will still be opensource, but the actual cuda work is done in the ptx assembly files compiled at runtime. The ptx files extracted from the free competition miners, modded to fit my miner. Free opensource speed boost. Without virus warnings. Even stealing takes time, much time is the stealer is sp_. With such speed of stealing you will always be far behind competitors. 0.6.7 t-rex is out already. I guess enemy 1.21 is not long to wait. |
|
|
|
 after block 191998 of 204284 synchronization is stopped what can I do to continue synchronization I was asking that in discord and was banned. Because I said that proposed "solution" to load blockchain as a zip file with higher blocks data then those around ~191997 is a crutch, not a solution as itself. Yes it works, but you will always need to do that if by some reason blockchain should sync from scratch. Dev is complaining about some windows update that spoils the sync. Dozens of other wallet sync - if they not sync their devs fix it. But this "dev" think that unability to sync from scratch is normal. Strange logic. |
|
|
|
The x17 profit is declining. The noob miners move to something more profitable...
That's the difference between private kernel code and public code.
Yes sure. I think the only "optimized"miner that is left in your stock is for spread algo. What if z/t will bother to make their's? |
|
|
|
kernels from cd/t-rex/enemy.
The best from cd/t-rex/enemy kernels is only giving 28MHASH on the 1080ti (x17). So I add the profitable percent. The +10% the other guys can't copy.. blablabla. Do first than talk. Who knows - maybe when you will accomplish adadtation of stolen kernels then z/t will do 35Mh. Whats the problem to write code? Lack of knowledge and abilities, isn't it? For the moment - your miner is the slowest, far behind z/t. Pity for you, but your time has passed. There is no alexis78 to stole code from Do you understand that t-rex, enemy and dredge release new version just after SP had made working speed-up code? Or you totally blind? They collect open source improvement, include it and propose with dev fee. If they only collect improvements then why they are faster? Why sp_ want to steal their kernels, if these kernels are just compiled from "his" opensource code? He can't compile, or he has no code? Something is completely wrong with your logic. |
|
|
|
kernels from cd/t-rex/enemy.
The best from cd/t-rex/enemy kernels is only giving 28MHASH on the 1080ti (x17). So I add the profitable percent. The +10% the other guys can't copy.. blablabla. Do first than talk. Who knows - maybe when you will accomplish adadtation of stolen kernels then z/t will do 35Mh. Whats the problem to write code? Lack of knowledge and abilities, isn't it? For the moment - your miner is the slowest, far behind z/t. Pity for you, but your time has passed. There is no alexis78 to steal code from Stealing kernels won't help you - it's a dead end. |
|
|
|
but for free
I have extracted all the kernels from the other devs and can soon publish a ptx opensource miner.. 30MHASH x17(asus 1080ti 90% tdp, +130 core +600 mem). 0.8% dev fee. Kernels made by t-rex/enemy/sp-mod. Thanks for the free work guys..  you now confessed that you are stealing code from other developers, it's very bad More than that - he confessed that he is incapable to make faster miner due to lack of skills. And the only option he has left is to steal kernels from cd/t-rex/enemy. |
|
|
|
I don't earn any money from my opensource work, but my private bins are getting faster and faster. X16R/X17 has improved to become +30% faster in a few months thanks to optimalizations. I made the 27MHASH x17 miner first.. Here is a post from August 8th. When enemy 1.14 and t-rex 5.7 was "the fastest" Still 20% slower than Enemy?
My private is around 20% faster than (enemy 1.14)/(t-rex 5.7) in x16r/x16s/x17 27 MHASH x17 1080ti, (2BTC) We all know how you "measure". 27Mh was "on paper". In reality maybe 23-24 was achieved. but for free What for free? Sp_ is talking about private miner. So 0.05BTC + dev fee that is mined at every start. So after each crash another devfee that is exactly in sp_ manner. |
|
|
|
I don't earn any money from my opensource work, but my private bins are getting faster and faster. X16R/X17 has improved to become +30% faster in a few months thanks to optimalizations. I made the 27MHASH x17 miner first.. Here is a post from August 8th. When enemy 1.14 and t-rex 5.7 was "the fastest" Still 20% slower than Enemy?
My private is around 20% faster than (enemy 1.14)/(t-rex 5.7) in x16r/x16s/x17 27 MHASH x17 1080ti, (2BTC) We all know how you "measure". 27Mh was "on paper". In reality maybe 23-24 was achieved. |
|
|
|
|
Show Posts
