Quote from: EVERYUSERNAMEISTAKEN on February 23, 2018, 07:29:29 AM

In an attempt to see if I could match earnings estimates, I decided to hop onto ahashpool for 24hrs. I had spent 72hrs on AHP before, and the results were less than satisfactory. That test is documented in my older posts if anyone's interested.

Equipment:

- 3 1080Tis @ 200w
- 1 1070Ti @ 150w

I downloaded the release of NPlusMiner 1.3 and I was on my way. I selected xevan, hsr, phi, tribus, x17, Nist5, Lyra2RE2, blake2s, and neoscrypt as my algos. I also selected skein, but again, it never stopped benchmarking so I just ditched it because I'm impatient. The benchmarking process yielded me 0.000061901 BTC; this amount will be subtracted from my first 24hrs later.

- My switching gain was 4%
- I suffered about 30 minutes of downtime
- The test started (benchmarking finished) on Feb 21 9:35pm. I stopped it at 10:35pm of the following day to account for the downtime.

I waited another 30 mins for any stray earnings to register. My total earned was 0.00118892 BTC. After subtracting the earnings from the benchmarking section, I'm left with 0.001127019 BTC. Let's break this down to what each card amounted to approximately:

- 1080Ti: 0.3 mBTC*3 cards = 0.9 mBTC
- 1070Ti: 0.22 mBTC*1 card = 0.22 mBTC

I haven't dabbled with any other Yiimp-based pools except for Zergpool briefly; most of my mining is from NH. In the same time frame, I've earned about 0.34-0.37 mBTC for each 1080Ti and about 0.23-0.26 mBTC for each 1070Ti. My actual earnings are usually within very close proximity to estimates. The greatest outlier I've seen was less than 5%. This leads me to my conclusion.

The good: After reaching 100% trust level in NPlus, the "average BTC/D" reading is extremely accurate. I still enjoy the UI, there's something classic about it.

The bugs: Skein benchmark never stops for me, this has happened to me twice in isolated situations.

The switching behaviour is also very strange. The first time I boot after finishing benchmarks, my sleep time is 30 secs. X17 is the most profitable at this time. As X17 warms up during this minute, the program sees that X17 is the most profitable algo, yet, it'll restart X17 and I gotta warm up again. Talking about warming up, without changing the default intensity, I warm up starting from around 53mh all the way to 70mh. Once in a while, I'll warm up from 64mh to 70mh. Not sure what's causing the latter, but I wish I could reproduce it. Takes about 10 mins to warm this damn thing up if I have to start from 53mh.

After my first round with 30 sec sleep time, it turns to 180 secs. I didn't touch the "-interval" option at all. It's not even in my batch file. HSR is now the most profitable algo. I think to myself "alright, the program probably just thinks it's temporary, so it hasn't switched algos". I wait for 20 minutes. The switcher hasn't refreshed once ever since sleep time turned to 180 secs. The computer isn't frozen and neither is the miner. I think to myself again "ah fuck it, X17 will probably be on top soon enough anyways, I'll just leave it and let's see how long it takes". Almost 2 hours pass and I can safely conclude it's probably a glitch at this point. I manually restart. After the reboot, we're back to 180 sec sleep time; the miner refreshes and switches properly now.

The ugly: Outside of the BTC/D from reaching 100% trust, the earnings estimates are still wildly inaccurate from my experience. I'm not sure why this is, but fuck AHP is all I'm saying.

Thanks for reading.

Thanks for testing and reporting.
Was this using ahashpoolplus?