 Show Posts
|
|
Pages: [1]
|
|
Thanks,
I have heard that someone has tried to program a software that could pause the mining so that the power will go down like the sleep but could be again start mining fast.
Adjusting power down fast is easy. Just shutdown or set to sleep but the difficult one is to start the mining again fast.
|
|
|
|
|
Hi,
We would need to control the site overall power draw and would need a tool to control the miner power draw pretty fast.
Its easy to shutdown the miner and power comes down fast, but are there any software that can stop the mining so that if can be restored fast too?
So the need is to toggle between few hundred watts and few kilowatts in less than 10 sec.
Thanks!
|
|
|
|
I have now run ~72 hours w/o any issues with 24 Vega64 GPUs(good and bad ones) mixed in 4 separate rigs ... CNR with core 1407Mhz /860-970mV , Mem 1080-1100Mhz/860-970mV.
I would say this is pretty stable setup. Pool side 24h avg hashrate fluctuates in the range 54,1-54,4 kH/s
--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 250
I am happy and have in my mind... "dont touch when things go smoothly".
That’s an insane voltage range, and I can’t fathom how 970mv could possibly be necessary. Between 9 64s and a flashed 56, I run avg 834mv, none over 850, for similar clocks/timings. That puts me @ 178w per GPU at the wall. At 970, you’re running at least 35% higher power, meaning over 240w per card. It sounds like you have some ppt issues or something, maybe you’re running your SOC @ 1200mhz unnecessarily (it should be 1107 @ your clocks.) Although, even then, you prob shouldn’t need much more than 925mv. Oops... I made a quick check with HWtool and yes... I really have SOC max @ 1199Mhz. I have used the Hellae 920mV PPT and then adjusted with Overdrive Ntool the Core P7 and Mem P3. I havent touch the SOC. After memory timings my rigs are pulling like 1420-1500w from the wall per rig. My rigs run like 150w w/o GPUs and after OverdriveNtool the wattage is ~250w before the miner starts and all the GPU led lights are fully on. This sounds to me like 1270 to 1350w with 6 GPU and on avg. like 210 - 225w/GPU. :O Thanks for pointing out the SOC. I need to drop to 1107. When I tried to scribble down a new Vega tuning guide to include in the TRM 0.4.4 release, I was debating if I should have mentioned this or not. I opted not to, that text was long enough already anyway. However, I know more than a few skilled and knowledgeable Vega tuners that ALL have been stuck with old PPTs from the fall of 2017 (brnsted, Hellae) that for some reason all have 1200 for SoC. At the time, I guess it was considered highly beneficial for stability. Fast forward a few years to times where you don't make $10/day/Vega and power draw is a crucial part of your setup, this trade-off no longer holds. In the common Google sheet ( https://docs.google.com/spreadsheets/d/1-rhYsaRXO1ahk3PyrEgT9gXzs7ImAzh-sbqtgwy8HQg) used for PPT tweaking you can edit the SOC clk value but guess what: it doesn't change any nrs in the PPT, the cells aren't connected(!!!). You have to change the SOC clk value in cell AE26, then manually copy cells AG-AI:26 to T-V:11. You can probably guess why I may sound a little pissed off  . Yeah.... I fixed my file so that these cell are now connected. Will test today what kind of mV I can get with 1107Mhz SOC. please post the PPT for reduced SOC.Thanks in advance. My initial findings.... so far stable rig with no hash rate drop(tested only one so far). Power draw from the wall dropped ~200w  (1450w -> 1250w). So if my rig w/o GPUs pull like 150w it means that 6xVega64 are now pulling like 1100w or ~185w/GPU. GPU_P0=852;860;0 GPU_P1=991;860;0 GPU_P2=1084;860;0 GPU_P3=1138;860;0 GPU_P4=1150;860;0 GPU_P5=1202;860;0 GPU_P6=1212;860;0 GPU_P7=1408;860 Mem_P0=167;860;0 Mem_P1=500;860;0 Mem_P2=800;860;0 Mem_P3=1100;860 Mem_TimingLevel=0 Fan_Min=3200 Fan_Max=3500 Fan_Target=75 Fan_Acoustic=2400 Power_Temp=85 Power_Target=-20 Fan_P0=24;11 Fan_P1=40;40 Fan_P2=48;60 Fan_P3=54;70 Fan_P4=60;85 Fan_ZeroRPM=0 Haven't yet tested to go lower.... |
|
|
|
I have now run ~72 hours w/o any issues with 24 Vega64 GPUs(good and bad ones) mixed in 4 separate rigs ... CNR with core 1407Mhz /860-970mV , Mem 1080-1100Mhz/860-970mV.
I would say this is pretty stable setup. Pool side 24h avg hashrate fluctuates in the range 54,1-54,4 kH/s
--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 250
I am happy and have in my mind... "dont touch when things go smoothly".
That’s an insane voltage range, and I can’t fathom how 970mv could possibly be necessary. Between 9 64s and a flashed 56, I run avg 834mv, none over 850, for similar clocks/timings. That puts me @ 178w per GPU at the wall. At 970, you’re running at least 35% higher power, meaning over 240w per card. It sounds like you have some ppt issues or something, maybe you’re running your SOC @ 1200mhz unnecessarily (it should be 1107 @ your clocks.) Although, even then, you prob shouldn’t need much more than 925mv. Oops... I made a quick check with HWtool and yes... I really have SOC max @ 1199Mhz. I have used the Hellae 920mV PPT and then adjusted with Overdrive Ntool the Core P7 and Mem P3. I havent touch the SOC. After memory timings my rigs are pulling like 1420-1500w from the wall per rig. My rigs run like 150w w/o GPUs and after OverdriveNtool the wattage is ~250w before the miner starts and all the GPU led lights are fully on. This sounds to me like 1270 to 1350w with 6 GPU and on avg. like 210 - 225w/GPU. :O Thanks for pointing out the SOC. I need to drop to 1107. When I tried to scribble down a new Vega tuning guide to include in the TRM 0.4.4 release, I was debating if I should have mentioned this or not. I opted not to, that text was long enough already anyway. However, I know more than a few skilled and knowledgeable Vega tuners that ALL have been stuck with old PPTs from the fall of 2017 (brnsted, Hellae) that for some reason all have 1200 for SoC. At the time, I guess it was considered highly beneficial for stability. Fast forward a few years to times where you don't make $10/day/Vega and power draw is a crucial part of your setup, this trade-off no longer holds. In the common Google sheet ( https://docs.google.com/spreadsheets/d/1-rhYsaRXO1ahk3PyrEgT9gXzs7ImAzh-sbqtgwy8HQg) used for PPT tweaking you can edit the SOC clk value but guess what: it doesn't change any nrs in the PPT, the cells aren't connected(!!!). You have to change the SOC clk value in cell AE26, then manually copy cells AG-AI:26 to T-V:11. You can probably guess why I may sound a little pissed off . Yeah.... I fixed my file so that these cell are now connected. Will test today what kind of mV I can get with 1107Mhz SOC. |
|
|
|
I have now run ~72 hours w/o any issues with 24 Vega64 GPUs(good and bad ones) mixed in 4 separate rigs ... CNR with core 1407Mhz /860-970mV , Mem 1080-1100Mhz/860-970mV.
I would say this is pretty stable setup. Pool side 24h avg hashrate fluctuates in the range 54,1-54,4 kH/s
--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 250
I am happy and have in my mind... "dont touch when things go smoothly".
That’s an insane voltage range, and I can’t fathom how 970mv could possibly be necessary. Between 9 64s and a flashed 56, I run avg 834mv, none over 850, for similar clocks/timings. That puts me @ 178w per GPU at the wall. At 970, you’re running at least 35% higher power, meaning over 240w per card. It sounds like you have some ppt issues or something, maybe you’re running your SOC @ 1200mhz unnecessarily (it should be 1107 @ your clocks.) Although, even then, you prob shouldn’t need much more than 925mv. Oops... I made a quick check with HWtool and yes... I really have SOC max @ 1199Mhz. I have used the Hellae 920mV PPT and then adjusted with Overdrive Ntool the Core P7 and Mem P3. I havent touch the SOC. After memory timings my rigs are pulling like 1420-1500w from the wall per rig. My rigs run like 150w w/o GPUs and after OverdriveNtool the wattage is ~250w before the miner starts and all the GPU led lights are fully on. This sounds to me like 1270 to 1350w with 6 GPU and on avg. like 210 - 225w/GPU. :O Thanks for pointing out the SOC. I need to drop to 1107. |
|
|
|
|
I have now run ~72 hours w/o any issues with 24 Vega64 GPUs(good and bad ones) mixed in 4 separate rigs ... CNR with core 1407Mhz /860-970mV , Mem 1080-1100Mhz/860-970mV.
I would say this is pretty stable setup. Pool side 24h avg hashrate fluctuates in the range 54,1-54,4 kH/s
--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 250
I am happy and have in my mind... "dont touch when things go smoothly".
|
|
|
|
The interleave adjustments aren’t always an indication of error, I have a few setups that need to adjust every 2 min or so per gpu. The 2100 h/s is the normal Vega 64 hashrate at 14*14 or 15*15 before memory timings are applied. Have you verified that the memory tweak tool applied your timings correctly?Last, what clocks are you using for your rigs? Indeed, I finally succeeded to get the --current values out from the rigs and it seems that the TRM 0.4.4. haven't managed to set updated timings on the GPUs that run with ~2100H/s... (all GPUs in the 3 rigs and one GPU from the 4th rig has still CL 20, REF 3900 RAS 33 RFC 260 etc. while other better performing 5 GPUs has CL 19, REF 15600, RAS 28, RFC 250). What it the reason TRM 0.4.4. haven't managed to update all the timings? Or should I do manually a .bat to get things set properly? I have so far just run the TRM 0.4.4. just like TRM 0.4.2. w/o any added parameters or anything. We don’t set those timings for you, everyone needs to download ElioVP’s tool themselves and include the timings mod in some .bat file . We don’t want to bundle it, it’s a slippery slope from a license perspective imho. I am thinking a little about building some flight control gui for TRM though that would be fully open source. No idea when I’ll get the time though... hmm.... Now I wonder how one of my rigs still have updated timings in 5 out of 6 GPUs  I did indeed wonder the same thing. Quite certain we didn’t set them for you  . [/quote] HAHA I found the reason My shortcut points to old .bat which have the config I used with TRM 0.4.2. Now I got all fixed.... thanks for the help... awesome miner and results! Thanks!!! |
|
|
|
The interleave adjustments aren’t always an indication of error, I have a few setups that need to adjust every 2 min or so per gpu. The 2100 h/s is the normal Vega 64 hashrate at 14*14 or 15*15 before memory timings are applied. Have you verified that the memory tweak tool applied your timings correctly?Last, what clocks are you using for your rigs? Indeed, I finally succeeded to get the --current values out from the rigs and it seems that the TRM 0.4.4. haven't managed to set updated timings on the GPUs that run with ~2100H/s... (all GPUs in the 3 rigs and one GPU from the 4th rig has still CL 20, REF 3900 RAS 33 RFC 260 etc. while other better performing 5 GPUs has CL 19, REF 15600, RAS 28, RFC 250). What it the reason TRM 0.4.4. haven't managed to update all the timings? Or should I do manually a .bat to get things set properly? I have so far just run the TRM 0.4.4. just like TRM 0.4.2. w/o any added parameters or anything. We don’t set those timings for you, everyone needs to download ElioVP’s tool themselves and include the timings mod in some .bat file . We don’t want to bundle it, it’s a slippery slope from a license perspective imho. I am thinking a little about building some flight control gui for TRM though that would be fully open source. No idea when I’ll get the time though... [/quote] hmm.... Now I wonder how one of my rigs still have updated timings in 5 out of 6 GPUs |
|
|
|
The interleave adjustments aren’t always an indication of error, I have a few setups that need to adjust every 2 min or so per gpu. The 2100 h/s is the normal Vega 64 hashrate at 14*14 or 15*15 before memory timings are applied. Have you verified that the memory tweak tool applied your timings correctly?Last, what clocks are you using for your rigs? [/quote] Indeed, I finally succeeded to get the --current values out from the rigs and it seems that the TRM 0.4.4. haven't managed to set updated timings on the GPUs that run with ~2100H/s... (all GPUs in the 3 rigs and one GPU from the 4th rig has still CL 20, REF 3900 RAS 33 RFC 260 etc. while other better performing 5 GPUs has CL 19, REF 15600, RAS 28, RFC 250). What it the reason TRM 0.4.4. haven't managed to update all the timings? Or should I do manually a .bat to get things set properly? I have so far just run the TRM 0.4.4. just like TRM 0.4.2. w/o any added parameters or anything. |
|
|
|
I wonder what is going on.... I have 4 x 6 Vega64 rigs. All running with the same setup (OS, drivers, versions etc.) When I applied the TRM 0.4.4 only one of my rigs got significant performance boost. In this very rig 5 out of 6 Vega64 has ~2400H/s but one still has ~2100H/s and the same one has also regular interleave adjustments. All the other GPUs in 3 rigs all have ~2100H/s and regular interleave adjustments. I would like all the rigs to perform like ~2400H/s per GPU, but wonder what could be wrong with the most of the GPUs and rigs? I tested 14*14 and seems that interleave adjustments are gone but hashrate remains ~2100H/s level per GPU. The interleave adjustments aren’t always an indication of error, I have a few setups that need to adjust every 2 min or so per gpu. The 2100 h/s is the normal Vega 64 hashrate at 14*14 or 15*15 before memory timings are applied. Have you verified that the memory tweak tool applied your timings correctly? Last, what clocks are you using for your rigs? I have optimized all the GPUs one by one. Rigs are stable now and Core is 1407Mhz with 860-970mV and Mem 1090-1100Mhz with 860-970mV. Power draw from the wall in these win10 rigs is 1320w in one rig and 1360-1370w rest of the rigs. All the rigs have mixed set of GPUs in terms of Core and Mem clocks. There is also one weird thing too. The rig that got the hashrate boost with TRM 0.4.4. have overall like 70w lower power draw from the wall than the other 3 rigs. Based on the mixed setup all the rigs should have ~ even power draw from the wall. I checked the HWinfo -> no signs of other differencies. My GPUs did like 2020-2060H/s with TRM 0.4.2. and w/o timing adjustments. So 0.4.4. gives slight improvement in all the rest 3 rigs but major boost only one of the rigs (5 out of 6 GPUs in that rig). Power draw from the wall increased 1320 -> 1420w and hashrate ~12%. In other 3 rigs hashes per GPU went only slightly up to ~2100H/s and rig power draw up like ~20-30w. |
|
|
|
I wonder what is going on.... I have 4 x 6 Vega64 rigs. All running with the same setup (OS, drivers, versions etc.) When I applied the TRM 0.4.4 only one of my rigs got significant performance boost. In this very rig 5 out of 6 Vega64 has ~2400H/s but one still has ~2100H/s and the same one has also regular interleave adjustments. All the other GPUs in 3 rigs all have ~2100H/s and regular interleave adjustments. I would like all the rigs to perform like ~2400H/s per GPU, but wonder what could be wrong with the most of the GPUs and rigs? I tested 14*14 and seems that interleave adjustments are gone but hashrate remains ~2100H/s level per GPU. |
|
|
|
|
Hi,
I have a quick question about the hash efficiency in Cryptonight Heavy.
I have noticed that Vega FE can make like + 2000H/s while Vega 64 can do like 1550H/s.
What kind of H/Watt does FE make? My Vega 64 does ~8.3H/Watt.
|
|
|
|
If I'd had a crystal ball I may have bought a Vega or 3 instead of all my 1070s but I reckon 3600 h/s @ 500W is pretty good no?
You can get that speed with 2 vegas @ 400W total power (cpu not hashing) Not in Cryptonight-heavy. About 1400 per Vega in that algo. 1070s seem on par with Vega in Cryptonite-Heavy to me. However 5 RX 570's can easily get 4000-4300 with about 500-550 watt. My 4x6 Vega 64 rigs in Cryptonight Heavy yields 37,2 kH/s with the power usage of 4440W (7 day average) This is just under 120W/kH. There is ~10% variability between my single GPU's. |
|
|
|
In long term if XHV will hit in the mainstream we should see the market cap to be hundreds of millions or even billions. This would mean 100x - 1000x. For now... just HODL and mine more with my 24x Vega64 @ 34KH/s. I would rather see again the low prices and get like +50XHV daily to my wallet |
|
|
|
|
I have now installed 4 rigs and automated the mining as much as I can. I even bought the wifi units that I can power off the rigs when I am travelling.
I have installed the hash monitor to reset the Cast XMR & set up the automatic power up after electric cut and set auto login with scheduled task to auto start the hash monitor and the miner.
Mining rigs can still fail so that my system cant restart and that is pretty annoying.
The whole operating system can freeze because of the GPU or driver instability. This has nothing to do with the cast XMR and the system needs kind of automated hard resetter to pass this kind of issue. This is quite rare and I currently handle this manually with the wifi electric plugs to power of the rig.
There is also another Cast XMR related issue I hope we can fix. Sometimes when one of the GPUs fails the Cast XMR continues with the rest of the GPUs for some time. Then it stops. Usually in this kind of situation the hash monitor doesnt get the input to restart the miner but just waits the hash drop restart criteria. Once the Cast XMR stops the hash monitor wont get any new data and the miner needs the manual restart.
It would be nice if Cast XMR would recognize if one of the GPUs fails (usually you can see it from the miner data log, normally you get log from all GPU0, GPU1, GPU2, GPU3, GPU4 and so on but suddenly the log miss one of the GPUs and the miner logs like GPU0, GPU1, GPU3, GPU4 and so on. In this case I would be nice if Cast XMR could automatically restart or terminate itself. This has been quite common issue in my rigs.
|
|
|
|
|
And just for the addition to the last posting...
I am running 4x6 units... total of 24 Vega 64....
And I an scared of ASICs or other systems that can make my investment crying.
Initial profit calculation was good with the payback time like few monts...
Now it has expanded to more than years... and I believe its because of the Bitmain silent and secret introduce of asics. I believe the used these by their own until they heard V7 and because of that decided to introduce X3 miners to the the market. They just want to get these out of their hands before it is too late.
So my perception is just dont buy these to prevent to be a victim of the scam.
BR.
Kerppa
|
|
|
|
|
Hi,
I am new in here but followed the discussion for a while.
I just got a question about the Monero upcoming fork. I do mine to Nicehash but am concerned a bit about the upcoming change.
I understood that Nicehash is supporting the upcoming XMV.
Please, can you clarify is the exact date to switch the algorithm to V7 6th April even the delayed snapshot date is now 30th April?
Then how about the cast miner, should I use still after the change in algorithm the option --algo=0 or what?
BR.
Kerppa from Finland
|
|
|
|
|
