Topic: Grin | Cuckoo POW | Benchmarking from c29 to c31 | Everything you need to know (Read 2134 times)

is there any mining software for Windows - 4GB AMD GPU ?
I found only for linux.

Seems that CryptoDredge v0.17.0 supports c29 for 9 days now.
Hopefully will get to try it later on the day.

Added.

I've been running Bminer v15.0 for a few days now. Some users were reporting stability issues, and I had some early with my prior overclocks, but running with stock core/memory and slight undervolt on SMOS, I've only had two restarts in a little over 3 days between two rigs. One rig has 2x 1080Ti (0/0/225W) + 2x 1080 (0/0/155W) and gets a combined 4.19gps poolside (miner reports 4.38gps) on C31 using Luxor, with less than 0.2% rejects. I haven't tested it on any other pools. If you're just looking at 1080Tis, mine report ~1.26 poolside (1.32gps on the miner). I've also got a 2080Ti running at 1.84gps poolside (miner reports 1.91gps) on C31. The new NBMiner looks interesting and I'd like to test it, but I have testing fatigue, so it'll probably be a few days before I get around to it.

New NBminer v20 is out, looking good for c31, achieving roughly Bminer v15 speeds.
So far zero rejected shares - small sample of course.
Interesting to see how this pans out.

On second thoughts maybe not. Depends on the rejected shares rate (Bminer).
Will know for sure tomorrow, unless someone else can confirm it.

With the new Bminer v15 reaching ~1.3 G/s on c31, turns out that it's definitely more profitable mining c29 ATM.

Alright, Bminer v15 on c31 gives 10%-15% invalid shares. That's a lot.
Regardless it's probably still worth it compared to GMiner (everything factored in).
Personally I just don't like unstable miners, so I will switch back to c29 & GMiner.

That said, looks like c29 is currently slightly more profitable than c31.

I'm sorry too man, writing in a manner of speech can be very confusing.
Thank you for your followup.

Also testing Bminer v15 on c31 as we speak, getting a ~1.3 per 1080ti - miner side.
Looking out for bad share rate & stability - will know for sure tomorrow.
From the little I tried it on c29, seems like nothing much has changed - still prefer GMiner v1.3.1 over Bminer v15 (or 14) for c29.

This took a wrong turn. I apologize because my bolded point (above) came across wrong. My intent was that instead of ME spewing numbers about, I'd just encourage you to test on your own - we may have different results based on where we live or our equipment, etc. I'm not blaming anyone for anything. I simply have observed different results than yours, those results have been consistent over several different versions of different miners, and those results match up with what others I've talked to have reported. Those results are that: 1) Bminer is significantly faster than Gminer on the poolside (especially, but not limited to C31); and 2) Gminer's reported hashrate is consistently higher than the pool reports, while Bminer's is the opposite. I've found this true on multiple pools, so I don't think its just an issue with the pool.

Having said all of that, I've found Bminer's latest version to be less stable and not underreporting hashrate compared to the pool for C29. For C31, it's rocking along on SMOS. Right now, I'm mostly mining C31 and get 1.91gps on my 2080Ti (0/0/225W), 1.3gps on each 1080Ti(0/0/225W), 0.87gps on each 1080(0/0/150W). I also get about 18.1gps using v 14.3.1 on my P106 x6(200/1500/80W) rig on C29.

OK. Bminer (v14 or v15) poorly supports cuckoo. It is very unstable. The difference in G/s compared to Gminer (v1.3.1) is minimal. Pool side. It's a fidelity thing.
And I don't just spew numbers out. A couple of posts back I meant (7.1 solid) miner side sure, but a few posts further back you can check exactly what you asked, and I answered for the second time. Only for you 'correct me' a third time round.

---

---

Instead of blaming others maybe you should read more.
Or maybe you should actually just contribute.

PS: Luxor is not advised as far as I'm concerned. Maybe it has a nice response where you live, but it's short of dodgy. It's the only pool I have lost coins in the past.

Firstly, I made a mistake in my prior post. I intended to say Bminer showed 6.0 gps (not 5.6gps), but poolside, I got 6.1 gps. You mentioned in your prior post that you were getting a solid 7.1 gps per card, but this post shows you're getting 6.5 gps poolside - that was my whole point. Gminer shows significantly higher hashrates than the pool, while other miners do not and/or it is less pronounced.


Rather than spewing numbers about, I'd encourage you to continue testing. I've tested Luxor, F2pool, sparkpool, and Grinmint using Minerbabe's Kbminer, Bminer, Gminer, and Grinminer on Linux (mostly SMOS) plus Bminer, Gminer, and Grinpro on Windows 10. I've done some with a P106 x6 rig + 2 1080s, 2 1080 Ti's, a 2070, and a 2080 Ti in various configurations. (Side note: Every time I add 20xx cards to a rig with 10xx cards on SMOS, one 10xx card fan will stop working correctly, so I have to separate them). I'm located in the southeast US, and in every test I've conducted, Luxor has shown lower rejects and higher reported hashrates than F2pool, sparkpool, on grinmint (in that order). Additionally, Gminer has always shown a higher hashrate than reported poolside, and Bminer has always shown a lower or equal hashrate to that reported poolside.

If you are only going to use Windows, I've found that, for my circumstances on the pools I've tried and the cards I have, Bminer 14.0+ shows better results than Gminer 1.31.

Running on sparkpool, with a nice average, using GMiner 1.3.1 on 4 X 1080ti's mining c29.
That would make it 6.5 G/s+ AVERAGE per ti. Reward wise as expected.
It could be your pool. You should try another one.

Did you confirm your hashrate poolside? I ran Gminer 1.3.1 for 24 hours on a 2070 and it showed 6.2-6.3 the whole time on the miner, but my 24hr pool hashrate was 5.6 for that period. Then I tried it on Bminer 14.3.1 and it showed 5.7 on the miner, but 6.1 at the pool. Both tests were ~24 hour periods, so it seems like its a legit result. Also, this matches what I observed a couple weeks ago when comparing Bminer vs Gminer using 1080s and 1080Ti's - the pool hashrate always was lower than Gminer reported, while the pool hashrate was always higher than what Bminer reported. I've read some others who said the same thing. All my testing was using Windows 10 and at Luxor for the 2070, but F2pool for the 1080s and 1080Ti's.

Grin added on Poloniex.

Gminer 1.3.2 is released, but has a fidelity bug - reporting low graph rate on the pool side.
Use of 1.3.1 for Grin is advised, until the new release.
Still not working for AMD.

Have tried in the past couple of days things with Bminer up to v14.3.1 on windows 10.
Have not succeed on getting it to run c31, despite upgrading to CUDA 10 and the latest NVDIA driver (418.81).
On c29 it runs OK-ish, without achieving the named speed (6.6 G/s instead of 7.1 G/s).

On the other hand GMiner v1.3.1 runs fine on both c29 & c31 - even with CUDA 9.
I get a solid 7.1 G/s per ti on c29, & 0.66 G/s for c31. Those are the best speeds I've seen so far for c29, c31 and windows.

It appears that Linux miners will always come first.

10x1070s I already have and 4 recently purchased 2080Ti. 

Nothing much new to report unfortunatelly.

c29 & c31 have roughly the same performance/rewards ATM.
Haven't had time to try the new Bminer on c31 yet, but I gather it's kind of buggy, so maybe another reason for taking this slow.

Grin listed on Bittrex today, added to exchanges.

got my 1080ti running under ubuntu on c31 using bminer 14.2.0 at grinmint. about 0.93 H/s

after maybe 15 mins its at 2 accepted, 4 rejected shares

sure its experimental c31 support but looks like more experimentation is in order.

EDIT went to 2 accepted, 6 rejected then bminer proclaimed "too many rejects" and restarted. then a bit later  i saw "no shares in 900 seconds" or something similar. and another restart.

EDIT 2 used ctrl-c to exit miner term session and the whole rig locked up.

think ill pass on bminer 14.4.0 c31 on grinmint for now

If your 1080ti is working fine, but not the 2080ti one, then probably it's the miner's fault - as you mentioned - the solver.
I would take it to their thread.