[ANN] TeamRedMiner - Old Thread

[peteris-apse]

Is this algo ram dependent? now i am having like 2.6-2.7 on vega 56 with 1350 on core and 300 mem, it is drawing like 200 per card from wall (my guess, i dont have data on this from remote computer).

[professorkuusamo]

vega 64 3,5 from wall 280w
vega 56 3,3 from wall 270w
settings like cryptonight r

[kerney666]

Is this algo ram dependent? now i am having like 2.6-2.7 on vega 56 with 1350 on core and 300 mem, it is drawing like 200 per card from wall (my guess, i dont have data on this from remote computer).

It is certainly ram dependent in that it needs ~4.5GB just to run. Given the mem access patterns, you can clock down memory a ton on Vegas (but not on Polaris cards), just like you've done. I actually think your core clk could be unnecessarily high, but the only way to know for sure is to continue tweaking. Since you're running on 300 memclk, I'm guessing you're already down in lower mem P-states? That is the preferred way since it will drop the soc clk, allowing for a much lower voltage for core + mem (as configured in e.g. OverdriveNTool). I've ran my tests down to 500 MHz memclk, but that's on Vega 64s.

You might already have read it, but I did write a little about the tuning process in the MTP_MINING.txt in the release package.

[kerney666]

vega 64 3,5 from wall 280w
vega 56 3,3 from wall 270w
settings like cryptonight r

Yes, the power draw is nuts even on standard CN clocks. Naturally it depends on your power cost, but in many cases you still earn a higher net profit using these crazy settings than clocking down and getting maybe 2.8-2.9 MH/s on a Vega 64 at a more reasonable (but still high) power draw. This algo will always pull a lot of power, it's by design unfortunately.

Compared to CN, you can seriously clock down mem though to save on power, it gives you a too small of a hashrate boost to justify the power draw. As stated above, details included in the release package in MTP_MINING.txt.

[kokodesu]

Thank you for adding MTP Argo.
It's a shame that you can not do it with a 4GB GPU, but it may be difficult.

win10
RX570 8G 1100/1800 about 1Mhz
RX580 8G 1340/2000 about 1.6Mhz

It was described in the wrong thread. I am sorry.

Thank you for testing! However, I must say your results are low compared to expected values, you should be able to hit ~1.6 MH/s (570) and ~1.8 MH/s (580) without too much tuning effort. I'll do a proper benchmark post soon, listing hashrates and settings for range of gpus.

Yes, I think my hash rate is low.
However, with regard to the problems of temperature and power, and with regard to the RX 570,
there is a present condition that is suppressed because it is an individual that can not make much memory OC.

In addition, there is also a thing that usually using HiveOS, there was also the aspect that it tested easily.

HiveOS
RX570 1100/875 1800/900 about 1.1Mhz
RX580 1100/875 2100/900 about 1.7Mhz

It is suppressed by the problem of temperature and power.

[kerney666]

Thank you for adding MTP Argo.
It's a shame that you can not do it with a 4GB GPU, but it may be difficult.

win10
RX570 8G 1100/1800 about 1Mhz
RX580 8G 1340/2000 about 1.6Mhz

It was described in the wrong thread. I am sorry.

Thank you for testing! However, I must say your results are low compared to expected values, you should be able to hit ~1.6 MH/s (570) and ~1.8 MH/s (580) without too much tuning effort. I'll do a proper benchmark post soon, listing hashrates and settings for range of gpus.

Yes, I think my hash rate is low.
However, with regard to the problems of temperature and power, and with regard to the RX 570,
there is a present condition that is suppressed because it is an individual that can not make much memory OC.

In addition, there is also a thing that usually using HiveOS, there was also the aspect that it tested easily.

HiveOS
RX570 1100/875 1800/900 about 1.1Mhz
RX580 1100/875 2000/900 about 1.7Mhz

It is suppressed by the problem of temperature and power.

Yes, you can definitely hit thermal throttling scenarios if the fans aren't cranked up high enough, or if you're in a warm location (like most of us this time of year).

[hbouma]

Team Red Miner v0.5.3 released

Now supporting the MTP algorithm for Zcoin

As mentioned at mintpond, the miner always exits when creating the scratchpad while being ran from awesome miner. I'll get the spinning cursor for a moment and then it will exit. If I try the diagnostic mode, it runs. If I run it using the included batch file, it works there too. So I'm not sure what is up. This is on Windows 10 with A6-3500 APU and RX 470 and RX 580 cards with 18.6.1. drivers. I've been mining with sgminer-fancyl and djm34's miner for weeks before this without problems I would think the settings/hardware should be fine to at least get the miner to start. lol.

Thanks for taking the time to add MTP support!

Hal

[kerney666]

Team Red Miner v0.5.3 released

Now supporting the MTP algorithm for Zcoin

As mentioned at mintpond, the miner always exits when creating the scratchpad while being ran from awesome miner. I'll get the spinning cursor for a moment and then it will exit. If I try the diagnostic mode, it runs. If I run it using the included batch file, it works there too. So I'm not sure what is up. This is on Windows 10 with A6-3500 APU and RX 470 and RX 580 cards with 18.6.1. drivers. I've been mining with sgminer-fancyl and djm34's miner for weeks before this without problems I would think the settings/hardware should be fine to at least get the miner to start. lol.

Thanks for taking the time to add MTP support!

Hal

Well that’s odd. Of course the hardware works fine if you can run it both in diagnostic mode and outside of AM . Not sure this is our issue (but it could very well be). Have you talked to the Awesome Miner guys? I’m traveling today but will try to test as soon as I can. I don’t have a good AM setup right now though but I’ll try to sort it out.

[joseph32]

Team Red Miner v0.5.3 released

Now supporting the MTP algorithm for Zcoin

As mentioned at mintpond, the miner always exits when creating the scratchpad while being ran from awesome miner. I'll get the spinning cursor for a moment and then it will exit. If I try the diagnostic mode, it runs. If I run it using the included batch file, it works there too. So I'm not sure what is up. This is on Windows 10 with A6-3500 APU and RX 470 and RX 580 cards with 18.6.1. drivers. I've been mining with sgminer-fancyl and djm34's miner for weeks before this without problems I would think the settings/hardware should be fine to at least get the miner to start. lol.

Thanks for taking the time to add MTP support!

Hal

Already made a post in Patrik's thread about that issue: https://bitcointalk.org/index.php?topic=676942.msg51710602#msg51710602

Edit @ Kerney: You can use just the standard setup. Its the same command line. In AM it crashs, without AM it runs. Would be great if we can sort out this bug.

[kerney666]

Team Red Miner v0.5.3 released

Now supporting the MTP algorithm for Zcoin

As mentioned at mintpond, the miner always exits when creating the scratchpad while being ran from awesome miner. I'll get the spinning cursor for a moment and then it will exit. If I try the diagnostic mode, it runs. If I run it using the included batch file, it works there too. So I'm not sure what is up. This is on Windows 10 with A6-3500 APU and RX 470 and RX 580 cards with 18.6.1. drivers. I've been mining with sgminer-fancyl and djm34's miner for weeks before this without problems I would think the settings/hardware should be fine to at least get the miner to start. lol.

Thanks for taking the time to add MTP support!

Hal

Already made a post in Patrik's thread about that issue: https://bitcointalk.org/index.php?topic=676942.msg51710602#msg51710602

Edit @ Kerney: You can use just the standard setup. Its the same command line. In AM it crashs, without AM it runs. Would be great if we can sort out this bug.

+1, I dropped a note in the AM thread as well.

[peteris-apse]

So Polaris is taking huge benefit from memory... Vegas not so much. Polaris rig is working great, but vegas...  I am still tweaking, but now i am having like weird problem with vegas where i cant get them stable. I guess i don't really understand how memory states affect core voltage. Because when i am starting to use other memory states it appears that it changes core voltage and my overclocks are not stable anymore.

[KL0nLutiy1]

@kerney666, could you please add ability to mining nimiq with your miner?

[kerney666]

Team Red Miner v0.5.3 released

Now supporting the MTP algorithm for Zcoin

As mentioned at mintpond, the miner always exits when creating the scratchpad while being ran from awesome miner. I'll get the spinning cursor for a moment and then it will exit. If I try the diagnostic mode, it runs. If I run it using the included batch file, it works there too. So I'm not sure what is up. This is on Windows 10 with A6-3500 APU and RX 470 and RX 580 cards with 18.6.1. drivers. I've been mining with sgminer-fancyl and djm34's miner for weeks before this without problems I would think the settings/hardware should be fine to at least get the miner to start. lol.

Thanks for taking the time to add MTP support!

Hal

Already made a post in Patrik's thread about that issue: https://bitcointalk.org/index.php?topic=676942.msg51710602#msg51710602

Edit @ Kerney: You can use just the standard setup. Its the same command line. In AM it crashs, without AM it runs. Would be great if we can sort out this bug.

Ok, the AM issues should be fixed in v0.5.4, todxx will update with the new release shortly.

[todxx]

Team Red Miner v0.5.4 released

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

Changes in v0.5.4

• Fixed API bug for MTP, crashing when using Awesome Miner.
• Small MTP improvements, mostly for Polaris.

A couple small fixes and improvements for mtp.

[dickmo]

hey,dude

Pool xzc.f2pool.com rpc method "mining.extranonce.subscribe" timed out after 69 seconds.  Reconnecting.

could you please take a look?

[todxx]

hey,dude

Pool xzc.f2pool.com rpc method "mining.extranonce.subscribe" timed out after 69 seconds.  Reconnecting.

could you please take a look?

Please try using the --pool_no_ensub option.

[dickmo]

hey,dude

Pool xzc.f2pool.com rpc method "mining.extranonce.subscribe" timed out after 69 seconds.  Reconnecting.

could you please take a look?

Please try using the --pool_no_ensub option.

Code:

2019-07-06 02:29:36] GPU 3 - MTP scratchpad rebuilt in 1.66 secs.
[2019-07-06 02:29:40] GPU 4 - MTP scratchpad rebuilt in 1.66 secs.
[2019-07-06 02:29:41] GPU 2 - MTP scratchpad rebuilt in 1.65 secs.
[2019-07-06 02:30:06] Stats Uptime: 0 days, 00:02:33
[2019-07-06 02:30:06] GPU 0 [63C, fan 91%] mtp: 2.795Mh/s, avg 2.710Mh/s, pool 894.8kh/s a:1 r:0 hw:0
[2019-07-06 02:30:06] GPU 1 [60C, fan 95%] mtp: 3.229Mh/s, avg 3.108Mh/s, pool 1.792Mh/s a:2 r:0 hw:0
[2019-07-06 02:30:06] GPU 2 [58C, fan 95%] mtp: 2.916Mh/s, avg 2.979Mh/s, pool 1.794Mh/s a:2 r:0 hw:0
[2019-07-06 02:30:06] GPU 3 [50C, fan 92%] mtp: 2.996Mh/s, avg 3.095Mh/s, pool 1.797Mh/s a:2 r:0 hw:0
[2019-07-06 02:30:06] GPU 4 [57C, fan 96%] mtp: 2.946Mh/s, avg 3.001Mh/s, pool 1.799Mh/s a:2 r:0 hw:0
[2019-07-06 02:30:06] Total                mtp: 14.88Mh/s, avg 14.89Mh/s, pool 8.077Mh/s a:9 r:0 hw:0
[2019-07-06 02:30:15] Pool xzc.f2pool.com set difficulty to 1023.984375
[2019-07-06 02:30:15] Pool xzc.f2pool.com received new job. (job_id: 02000000)
[2019-07-06 02:30:36] Stats Uptime: 0 days, 00:03:03
[2019-07-06 02:30:36] GPU 0 [64C, fan 91%] mtp: 2.815Mh/s, avg 2.727Mh/s, pool 745.6kh/s a:1 r:0 hw:0
[2019-07-06 02:30:36] GPU 1 [60C, fan 95%] mtp: 3.229Mh/s, avg 3.132Mh/s, pool 1.493Mh/s a:2 r:0 hw:0
[2019-07-06 02:30:36] GPU 2 [58C, fan 95%] mtp: 3.086Mh/s, avg 3.001Mh/s, pool 1.495Mh/s a:2 r:0 hw:0
[2019-07-06 02:30:36] GPU 3 [51C, fan 92%] mtp: 3.229Mh/s, avg 3.121Mh/s, pool 1.496Mh/s a:2 r:0 hw:0
[2019-07-06 02:30:36] GPU 4 [57C, fan 96%] mtp: 3.118Mh/s, avg 3.019Mh/s, pool 1.498Mh/s a:2 r:0 hw:0
[2019-07-06 02:30:36] Total                mtp: 15.48Mh/s, avg 15.00Mh/s, pool 6.727Mh/s a:9 r:0 hw:0
[2019-07-06 02:31:06] Stats Uptime: 0 days, 00:03:33
[2019-07-06 02:31:06] GPU 0 [63C, fan 91%] mtp: 2.808Mh/s, avg 2.739Mh/s, pool 639.1kh/s a:1 r:0 hw:0
[2019-07-06 02:31:06] GPU 1 [60C, fan 95%] mtp: 3.163Mh/s, avg 3.134Mh/s, pool 1.279Mh/s a:2 r:0 hw:0
[2019-07-06 02:31:06] GPU 2 [58C, fan 95%] mtp: 3.085Mh/s, avg 3.012Mh/s, pool 1.281Mh/s a:2 r:0 hw:0
[2019-07-06 02:31:06] GPU 3 [51C, fan 92%] mtp: 3.229Mh/s, avg 3.135Mh/s, pool 1.282Mh/s a:2 r:0 hw:0
[2019-07-06 02:31:06] GPU 4 [57C, fan 96%] mtp: 3.089Mh/s, avg 3.027Mh/s, pool 1.283Mh/s a:2 r:0 hw:0
[2019-07-06 02:31:06] Total                mtp: 15.37Mh/s, avg 15.05Mh/s, pool 5.764Mh/s a:9 r:0 hw:0

it works ,thanks
GPU0=vega56
orthers=vega64

power per card 200w

[joseph32]

Hey Todxx & Kerney666,

thanks for the quick fix! It runs now perfect with AwesomeMiner!

[todxx]

Team Red Miner v0.5.5 released

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

Changes in v0.5.5

• Added cuckatoo31 algo for grin.

We've added cuckatoo31 for grin mining!
Seems we might have been a bit late as asics are might already be here for the algo  .

[ku4eto]

Team Red Miner v0.5.5 released

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

Changes in v0.5.5

• Added cuckatoo31 algo for grin.

We've added cuckatoo31 for grin mining!
Seems we might have been a bit late as asics are might already be here for the algo  .

They have been up since the coin launched.