 Show Posts
|
|
Pages: [1]
|
Definitely interesting at the very least since on their website they claim to be "built on an entirely new chain". Assuming PIRL is built on an early version of ETH (or perhaps the ETH genesis?), isn't this a windfall for the ETH developers who hold the private keys for these addresses? This issue needs to be publicly addressed by the dev team. |
|
|
|
|
What really raises my eyebrows is how, during a time when Tether isn't accepting any new customers, nor is it allowing existing customers to deposit new funds was Tether able to issue $600M new USDT on Saturday, Jan 27?
|
|
|
|
Thx, for providing this data.
You have a lot 'nvidia-settings' processes running in your 'After top' output. This could be the reason for the performance drop.
Just to add my voice to this list, I'm also an SMOS user experiencing the same issue. HOWEVER, it's only on my 13 card 1070 rigs (H110). I have a 6 card 1060 rig (Z270-A) that has been running for days with no drop in performance, also on SMOS. Thanks for being responsive! UPDATE: For me, the problem seems to have gone away with v0.5.7. 24 hours solid now with no performance dropoff. Added 2 more 13 card rigs about 8 hours ago and all seems solid. |
|
|
|
Is it normal for hash rate to drop by half on DSTM miner console, NOT on pool hash rate. I am mining equihash on nicehash or miningpoolhub.
I cant understand why it does this. The gpus are not overheating or crashing. It is just a massive reduction in hash rate that's fixed by reboot of console.
It changes the difficulty rate and then drops.
I'm having the same issue trying v0.5.6 and v0.5.7. It starts out around 4,600 Sol/s and it slowly drops to around 2,000 Sol/s over the course of a couple of hours. Running SMOS and have tried mining several equihash coins at a couple of different pools with the same results. Rebooting makes it go back up to 4,600 Sol/s it then it slowly drops down again. Temperatures are all <55C with a target of 75C. Servers seem to be changing GPU difficulties often. Overclocks set to 0 while I try to figure this out. Same issue here, playing card roulette right now. It seems to only happen when one of my cards is in, what I have done so far: 1. Removed all overclocks 2. Watt use is at 110 for 1070ti's, 120 for 1070, and 200 for 1080ti's (note: all hash rates drop, the 1080ti's in particular hit the 500's) 3. Swapped entire riser on suspect gpu 4. Swapped pci ports, tested pci port with alternative gpu 5. Looked at wattage use of cards when they drop, cards all drop power down well below my set wattage. So the power drop I think is the cause of less hash, what's causing the power drop I am unsure of. Smos dtsm 0.5.6 (trying 5.7 now) 10 cards currently (have had various amounts between 9-13) h110 pro btc EDIT: So far so good on new version, but judging by change log this is just luck right now. I have the same issue. Hashrate decreases after running a time (few hours). Tested on SMOS dstm-v0.5.8 (0.5.7, 0.5.6 is same) 5 Rig P106-100 x12 (on main H110 Pro BTC) When the hashrate dropped, the screen appeared a lot of duplicated share message, at the same time cpu usage is very high. However, sometimes I can run nearly a day that hashrate not decrease.  Judging by the reports this seems to affect SMOS users only. How do you monitor the solution rate on SMOS, does it provide a custom interface? Could you also pls provide the output of the 'top' command sorted by cpu usage and the output of nvidia-smi, before and after the solution rate drop? OK. I can moniter SMOS via ssh client (putty) Test on SMOS (P106-100 x12) Non OC Power Limit: 80W dstm-v0.5.8 Best regards. Thx, for providing this data. You have a lot 'nvidia-settings' processes running in your 'After top' output. This could be the reason for the performance drop. Just to add my voice to this list, I'm also an SMOS user experiencing the same issue. HOWEVER, it's only on my 13 card 1070 rigs (H110). I have a 6 card 1060 rig (Z270-A) that has been running for days with no drop in performance, also on SMOS. Thanks for being responsive! |
|
|
|
Only thing that pops in my mind would be the cards are stuck at lower clock state somehow. Tried monitoring the clock speeds with nvidia-smi?
Didn't even know that was a thing. I'll give it a try, thanks for the suggestion! |
|
|
|
Has anyone had experience with this miner dropping hash rate significantly over time?
I have 2 rigs each with 13 x 1070s running on SMOS. The rigs start out at a delicious 6300 sol/s, but over about 8 hours drop steadily to about 3500 sol/s.
Obviously this is a non starter for me. My only guess is perhaps the CPU is getting overwhelmed with so many cards in the rig? I'm no Linux expert so I don't know how I'd even check that.
ruled out anything related to temp target set in config file? Good question. I'm not using a config file, just booting from command line. I didn't set --temp-target so this feature should not be active. Here's my command line: --server <servername> --port <portname> --user <myusername>.<myrigname> --pass <mypass> --time --telemetry=0.0.0.0:42000 Obscured my actual settings with <variables> but you get the drift. |
|
|
|
|
Has anyone had experience with this miner dropping hash rate significantly over time?
I have 2 rigs each with 13 x 1070s running on SMOS. The rigs start out at a delicious 6300 sol/s, but over about 8 hours drop steadily to about 3500 sol/s.
Obviously this is a non starter for me. My only guess is perhaps the CPU is getting overwhelmed with so many cards in the rig? I'm no Linux expert so I don't know how I'd even check that.
|
|
|
|
|
