clock 1366 mem 1750 undervolt -120
What power consumption? 
Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 25. (Read 85791 times)
February 03, 2019, 09:43:53 AM
February 03, 2019, 09:20:28 AM
After 2h5m no rejected 
impressive!
impressive! February 03, 2019, 07:34:25 AM
clock 1366 mem 1750 undervolt -120
February 03, 2019, 07:33:28 AM
RX580 4GB Pulse (Elpida) stock bios strap 1500+ and undervolt -120
54.4 MHs lyra2rev3
54.4 MHs lyra2rev3
Slight performance improvement on 0.3.10 release
54.4 to 54.7
February 03, 2019, 07:23:21 AM
RX580 4GB Pulse (Elpida) stock bios strap 1500+ and undervolt -120
54.4 MHs lyra2rev3
54.4 MHs lyra2rev3
Slight performance improvement on 0.3.10 release
54.4 to 54.7
no rejected in 40 min
February 03, 2019, 07:21:19 AM
Don't see any improve in 10 version compared with 9 for lyra2rev3 and Vega56 under Windows, but rejected shares gone away
February 03, 2019, 06:28:10 AM
Dear developers how can I contact you?
February 03, 2019, 05:27:18 AM
Team Red Miner v0.3.10 released
https://github.com/todxx/teamredminer/releases
Changes in v0.3.10
Most of the changes in this release are fixes for various issues people ran into with lyra2rev3.
Issues seen with p2pool and bitpoolmining should now be resolved.
There was also a small performance improvement for Vegas in this version
Edit: For those of you running with p2pool (or coinotron), you may need to add the following option to your command line: --pool_no_ensub
https://github.com/todxx/teamredminer/releases
Changes in v0.3.10
- Slight performace improvement for Vegas on lyra2rev3
- Pool stratum protocol work-arounds for some pools, fixing duplicate share error.
- Changed handling of unrecognized pool rpcs to be ignored instead of causing a reconnect.
- Fix for duplicate shares on 480/580/Vega56 cards with lyra2rev3.
Most of the changes in this release are fixes for various issues people ran into with lyra2rev3.
Issues seen with p2pool and bitpoolmining should now be resolved.
There was also a small performance improvement for Vegas in this version
Edit: For those of you running with p2pool (or coinotron), you may need to add the following option to your command line: --pool_no_ensub
February 03, 2019, 04:43:16 AM
I'm getting 58.8Mhs@135Wt with Fury cards in lyra2rev3. Though they are 60CU, not 56.
February 03, 2019, 01:44:40 AM
How to lower intensity for lyra2rev3? I get 52 MH/s on RX 580 8Gb. But power consumption is too high. About 140-150W. It's need intensity option to lower power cons.
Hi! You need to control power draw (and perf) using your clocks, it's just the correct way to do it. Intensity is such a bogus idea for AMD cards for compute algos that doesn't allocate much mem. You're asking for a way to lower the global size of the scheduled jobs to the point where the card runs much less efficiently because of scheduling overhead and execution micro-variance having a larger effect on the overall hashrate. However, that also increases PCIe chatter and host-side load (that is tiny though).
Hence, the proper approach is to tweak clocks and voltages until you end up with a power draw profile you're comfortable with. For CN, we provide ways of tweaking "intensity", but that's a very different ballgame.
February 03, 2019, 12:54:07 AM
@kerney666, what about MTP algo, do you plan to add it?
The main part of MTP is dead simple, I'm truly amazed there aren't good open source miners out there already.
For the algos we add to this miner, we only select those where we truly feel we can add enough persistent value to warrant a higher-than-normal dev fee. MTP should/will have good miners shortly, or it's really an embarrasing fail for open source in crypto. Moreover, with the hack they've added with a binary stratum protocol to keep effective bandwidth down, this is a ton of work for us in this miner. Otoh, it would be very simple to add it to e.g. a sgminer clone. Last, I think AMD cards will have a hard time beating Nvidia from an efficiency perspective for this algo, which also means adoption might be much smaller than you'd hope for as a miner dev.
Given all this, the probability that we would ever get the time spent on MTP back is tiny, so we've opted not to do it. Tbh, if I had the time I would rather spend it on an open source implementation.
Kerney666 its been more than 2 months, i think a high fee can be warranted still no stable amd miners available bro.
Yeah, I'm still amazed. I haven't kept track of what djm34 and fancyIX ended up with though, is it still crap? Last I checked they were getting closer to the nrs I would expect, 580 maybe 1.4-1.6 MH/s, Vegas should be able to do 3.1-3.5 MH/s. You need the compute for MTP, so 64s will outperform 56s.
February 03, 2019, 12:45:52 AM
I have dedicated a mining rig to mine vtc. So far my hash rate is about 82 mh/s per vega 56 using cnv8 settings for a total of about 250 mh/s for the rig, measuring 700 watts at the wall. This is my first time mining this algorithm so i am not sure if that good but that is around 130 watts more than what i get mining monero. I'm on the 0.3.9 version and easy mine pool.
So far in my hour of mining i have a 2% rejected shares. The error i keep seeing most is the duplicate share error22. I would like to get that to as close to 0% as possible.
So far in my hour of mining i have a 2% rejected shares. The error i keep seeing most is the duplicate share error22. I would like to get that to as close to 0% as possible.
New release coming out in a few hours that fixes a few issues with pools mistreating the stratum protocol and also a bug for 580s and Vega 56s that could cause dup shares. Look out for it, then let us know if you're still seeing the issue, I believe it'll disappear though.
February 02, 2019, 11:10:15 PM
I have dedicated a mining rig to mine vtc. So far my hash rate is about 82 mh/s per vega 56 using cnv8 settings for a total of about 250 mh/s for the rig, measuring 700 watts at the wall. This is my first time mining this algorithm so i am not sure if that good but that is around 130 watts more than what i get mining monero. I'm on the 0.3.9 version and easy mine pool.
So far in my hour of mining i have a 2% rejected shares. The error i keep seeing most is the duplicate share error22. I would like to get that to as close to 0% as possible.
So far in my hour of mining i have a 2% rejected shares. The error i keep seeing most is the duplicate share error22. I would like to get that to as close to 0% as possible.
February 02, 2019, 09:44:05 PM
@kerney666, what about MTP algo, do you plan to add it?
The main part of MTP is dead simple, I'm truly amazed there aren't good open source miners out there already.
For the algos we add to this miner, we only select those where we truly feel we can add enough persistent value to warrant a higher-than-normal dev fee. MTP should/will have good miners shortly, or it's really an embarrasing fail for open source in crypto. Moreover, with the hack they've added with a binary stratum protocol to keep effective bandwidth down, this is a ton of work for us in this miner. Otoh, it would be very simple to add it to e.g. a sgminer clone. Last, I think AMD cards will have a hard time beating Nvidia from an efficiency perspective for this algo, which also means adoption might be much smaller than you'd hope for as a miner dev.
Given all this, the probability that we would ever get the time spent on MTP back is tiny, so we've opted not to do it. Tbh, if I had the time I would rather spend it on an open source implementation.
Kerney666 its been more than 2 months, i think a high fee can be warranted still no stable amd miners available bro.
February 02, 2019, 07:45:54 PM
Are there any plans for XTL to be mineable with Teamredminer???
February 02, 2019, 02:41:47 PM
what is the expected hashrate for vega 56? Currently my 64s/FEs are getting almost twice as much as the 56s
Quite unexpected, should be roughly linear in CUs, 56/64s of what the Vega 64s are doing. What are your clocks and current results?
@Kerney, fault is mine... the problem had to do with previously mining GRIN on these cards... the GRIN miner set some global environment variables that screwed with mining other algo's... problem fixed now!
February 02, 2019, 02:41:06 PM
How to lower intensity for lyra2rev3? I get 52 MH/s on RX 580 8Gb. But power consumption is too high. About 140-150W. It's need intensity option to lower power cons.
Hi! You need to control power draw (and perf) using your clocks, it's just the correct way to do it. Intensity is such a bogus idea for AMD cards for compute algos that doesn't allocate much mem. You're asking for a way to lower the global size of the scheduled jobs to the point where the card runs much less efficiently because of scheduling overhead and execution micro-variance having a larger effect on the overall hashrate. However, that also increases PCIe chatter and host-side load (that is tiny though).
Hence, the proper approach is to tweak clocks and voltages until you end up with a power draw profile you're comfortable with. For CN, we provide ways of tweaking "intensity", but that's a very different ballgame.
February 02, 2019, 02:39:55 PM
How to lower intensity for lyra2rev3? I get 52 MH/s on RX 580 8Gb. But power consumption is too high. About 140-150W. It's need intensity option to lower power cons.
Hi! You need to control power draw (and perf) using your clocks, it's just the correct way to do it. Intensity is such a bogus idea for AMD cards for compute algos that doesn't allocate much mem. You're asking for a way to lower the global size of the scheduled jobs to the point where the card runs much less efficiently because of scheduling overhead and execution micro-variance having a larger effect on the overall hashrate. However, that also increases PCIe chatter and host-side load (that is tiny though).
Hence, the proper approach is to tweak clocks and voltages until you end up with a power draw profile you're comfortable with. For CN, we provide ways of tweaking "intensity", but that's a very different ballgame.
I see. Well, that’s at least a good argument for slowing down mining on that gpu even if it’s what I’d call a dumb way of doing it. Let me ponder a bit, I still think there are better ways of achieving a deliberate slowdown.
February 02, 2019, 02:25:36 PM
How to lower intensity for lyra2rev3? I get 52 MH/s on RX 580 8Gb. But power consumption is too high. About 140-150W. It's need intensity option to lower power cons.
Hi! You need to control power draw (and perf) using your clocks, it's just the correct way to do it. Intensity is such a bogus idea for AMD cards for compute algos that doesn't allocate much mem. You're asking for a way to lower the global size of the scheduled jobs to the point where the card runs much less efficiently because of scheduling overhead and execution micro-variance having a larger effect on the overall hashrate. However, that also increases PCIe chatter and host-side load (that is tiny though).
Hence, the proper approach is to tweak clocks and voltages until you end up with a power draw profile you're comfortable with. For CN, we provide ways of tweaking "intensity", but that's a very different ballgame.
February 02, 2019, 01:27:12 PM
what is the expected hashrate for vega 56? Currently my 64s/FEs are getting almost twice as much as the 56s
Quite unexpected, should be roughly linear in CUs, 56/64s of what the Vega 64s are doing. What are your clocks and current results?
Jump to: