Re: PhoenixMiner 2.8c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Report of first 24hrs on PhoenixMiner 2.9d (migrated from 2.8c).
Environment: 52 GPU (45x RX580/8GB, 7x 1070/8GB) in four rigs of 13 cards each.
Results:
- Hashing rate: Increased a bit: Before: 1.630 GH/s, now 1.633 GH/s ~ 0.12% increase. The increase is most notable on Nvidia cards.
- Power Consumption: Decreased for few watts: e.g. on one rig from 1630 to 1620W on average, measured on the wall. A slight temperature drop in line with power consumption.
- Stale share: Increased a bit as reported by the ethermine.org pool, before 3-4%, now 4-5% with drops to 2% occasionally. Was < 3% on Claymore 11.5
- Stability: Stable, occasional hashing drops on some cards e.g. form 31MH/s to 24 for a 10-20 sec, then recovering back to normal 31 MH/s. Did not observe that before.
Comments:
- In my opinion the "-logsmaxsize Maximum size of the logfiles in MB. The default is 200 MM"; The default value of 200Mb is to high and cannot be normally edited by most editors. The default should be no more than e.g. 10MB or if you must, 50Mb.
- Missing a feature: Auto tune of the GPU tuning parameter /-gt/; Similar to Claymore -dcri auto tune).
- The 2.9d is officially released as an unofficial version with full support. Really
Why not just stick to the usual sw naming convention like calling it "alpha"; a limited test version that might get new functionalities until released as final.
Verdict: Works like a charm out of the box. Thumbs up!
Environment: 52 GPU (45x RX580/8GB, 7x 1070/8GB) in four rigs of 13 cards each.
Results:
- Hashing rate: Increased a bit: Before: 1.630 GH/s, now 1.633 GH/s ~ 0.12% increase. The increase is most notable on Nvidia cards.
- Power Consumption: Decreased for few watts: e.g. on one rig from 1630 to 1620W on average, measured on the wall. A slight temperature drop in line with power consumption.
- Stale share: Increased a bit as reported by the ethermine.org pool, before 3-4%, now 4-5% with drops to 2% occasionally. Was < 3% on Claymore 11.5
- Stability: Stable, occasional hashing drops on some cards e.g. form 31MH/s to 24 for a 10-20 sec, then recovering back to normal 31 MH/s. Did not observe that before.
Comments:
- In my opinion the "-logsmaxsize Maximum size of the logfiles in MB. The default is 200 MM"; The default value of 200Mb is to high and cannot be normally edited by most editors. The default should be no more than e.g. 10MB or if you must, 50Mb.
- Missing a feature: Auto tune of the GPU tuning parameter /-gt/; Similar to Claymore -dcri auto tune).
- The 2.9d is officially released as an unofficial version with full support. Really
Why not just stick to the usual sw naming convention like calling it "alpha"; a limited test version that might get new functionalities until released as final.Verdict: Works like a charm out of the box. Thumbs up!