Post
Topic
Board Mining (Altcoins)
Re: [ANN] TeamRedMiner 0.4.0 - CN v8/R - Vega 64 2200+h/s Rx470 1025+h/s Low Power
by
pbfarmer
on 09/03/2019, 10:40:32 UTC
Team Red Miner v0.4.0 released

https://github.com/todxx/teamredminer/releases

Changes in v0.4.0
  • Added cryptonight R support.  (--algo cnr)
  • Added support for ssl/tls pool connections using the stratum+ssl:// prefix.
  • Added colors (and an option to disable them).
  • Slight performance increase for lyra2rev3 (~0.5%).
  • Fix for occasional crashes when pool disconnects.
  • Added more messages regarding not being connected to dev pool.
  • Changed printing to not block mining progress if stdout writes block.

A bit delayed with this post, but better late than never.

The main change in this version is the addition of CN/R support.
Performance of CN/R is roughly the same on Vegas as cnv8.  Polaris cards are a bit slower with larger cards losing about 0.5% and the smaller cards like rx550s losing ~1.5%.
Power for CN/R is up by 2-3% compared to cnv8.

Also we've added some user requested features like colors and support for ssl pool connections.


Hi,
I have problem with Vega and CryptonightR.
Intensity set to 12+11. (14+14, 14+13 hangs my cards)
And I have this results:
Code:
[2019-03-09 11:10:54] Stats Uptime: 0 days, 00:09:01
[2019-03-09 11:10:54] GPU 0 [34C, fan  0%] cnr: 2.811kh/s, avg 1.403kh/s, pool 2.235kh/s a:5 r:0 hw:0
[2019-03-09 11:10:54] GPU 1 [34C, fan  0%] cnr: 2.825kh/s, avg 1.413kh/s, pool 2.982kh/s a:7 r:0 hw:0
[2019-03-09 11:10:54] GPU 2 [29C, fan  0%] cnr: 2.800kh/s, avg 1.399kh/s, pool 1.491kh/s a:3 r:0 hw:0
[2019-03-09 11:10:54] GPU 3 [31C, fan  0%] cnr: 3.053kh/s, avg 1.523kh/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-09 11:10:54] Total                cnr: 11.49kh/s, avg 5.739kh/s, pool 6.708kh/s a:15 r:0 hw:0
[2019-03-09 11:11:10] Shutting down...
[2019-03-09 11:11:11] GPU 2 CN thread 1 exiting.
[2019-03-09 11:11:11] GPU 3 CN thread 0 exiting.
[2019-03-09 11:11:11] GPU 0 CN thread 1 exiting.
[2019-03-09 11:11:11] GPU 1 CN thread 1 exiting.
[2019-03-09 11:11:20] GPU 0 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 1 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 2 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 3 thread 1 shutdown timed out.

1. 2.8kh/s is rather high. Avarage is a half of this.

Intensity 13+12
Code:
[2019-03-09 11:21:02] GPU 0 [ 0C, fan  0%] cnr: 3.060kh/s, avg 1.525kh/s, pool 1.579kh/s a:2 r:0 hw:0
[2019-03-09 11:21:02] GPU 1 [ 0C, fan  0%] cnr: 3.072kh/s, avg 1.531kh/s, pool 1.579kh/s a:3 r:0 hw:0
[2019-03-09 11:21:02] GPU 2 [ 0C, fan  0%] cnr: 3.044kh/s, avg 1.517kh/s, pool 395.0 h/s a:1 r:0 hw:0
[2019-03-09 11:21:02] GPU 3 [ 0C, fan  0%] cnr: 3.050kh/s, avg 1.520kh/s, pool 2.371kh/s a:4 r:0 hw:0
[2019-03-09 11:21:02] Total                cnr: 12.22kh/s, avg 6.093kh/s, pool 5.923kh/s a:10 r:0 hw:0
2. I have trouble with shutdown. After that I have to force miner to close the window.



1. I'm on linux, but I'm seeing similar behavior to what I saw w/ cnv2 on Windows - for vega64, an effective core clock of 1400MHz, mem clock 1107, and voltage around 830-850mv should get you 2.1Kh/s w/ 16+14. 

2. The failure mode resulting from too much oc/uv can be pretty harsh - often you see a full opencl/driver crash, sometimes requiring a reboot or even hard reset.