2018-10-13 03:30:56
@mjay @Rotonen I'm almost totally sure it's because of my internet connection. I have 2 locations, both wireless connections, and one has better line of sight than the other. I moved one box over to the location with better LOS and it is hashing more consistently with the other. I'm going to do some speed tests as well and probably upgrade service. Thanks so much for the ideas of what could be wrong.
aikida3k
2018-10-13 04:08:31
your internet connection sounds being worse than here in Germany.
fydel
2018-10-13 04:10:03
you live in antarctica? with the all penguins?
fydel
2018-10-13 04:12:36
haha. but after no joking your mining speed should not depend on your line speed. unless you are using a 56k modem.
fydel
2018-10-13 04:17:39
If you are doing arktika with remote layers it would matter
Fireduck
2018-10-13 04:26:08
yes sure. but i think he was talking of mining to pools.
fydel
2018-10-13 04:26:23
Sure
Fireduck
2018-10-13 07:09:44
i’m not sure what is used there, but 10GE would be the right thing to use for remote layers at a decent price point
Rotonen
2018-10-13 09:27:30
I get these reply times an order of magnitude (10x) longer than expected at some intervals. As far as I can tell, this is what is affecting my hash rate. With the box I moved over to the other location with better LOS, that box is getting the same hash rate as the other.
aikida3k
2018-10-13 09:29:23
I will do some tests tomorrow at the other location and see what it looks like, but this is a reasonable explanation I can come up with why the hash rate is much less than expected.
aikida3k
2018-10-13 09:29:30
as far as i can see, you're still not telling how you mine - arktika? chunks over a networked filesystem?
Rotonen
2018-10-13 09:29:58
With these I am mining with the pool miner
aikida3k
2018-10-13 09:30:21
ping should not matter, you only post a result per minute to the pool if the difficulty thingy works proper
Rotonen
2018-10-13 09:31:08
and only look at the 1h average hash rate the miner gives you, everything else is just noise
Rotonen
2018-10-13 09:36:12
If the ping time reply doesn't matter, I don't see why my hash rate would be cut nearly in half. I know when I mined with arktika, when I had a suboptimal cable that brought that link in the network down to 100Gbs my hash rate for that node was cut in half. When I replaced the cable so the link became 1000 Gbs (order of magnitude) my hash rate doubled.
aikida3k
2018-10-13 09:44:18
what do you mean when you say 'hash rate'?
Rotonen
2018-10-13 09:46:44
The reading given for 1 min, 5 min, and 1 hour
aikida3k
2018-10-13 09:47:00
and you say the 1 hour one cuts in half when you wait 2 hours?
Rotonen
2018-10-13 09:47:06
yes
aikida3k
2018-10-13 09:47:57
@Fireduck you might want to look into any networking code which is blocking in the pool miner ^
Rotonen
2018-10-13 09:47:58
At the other location. At the location with better LOS, the 1 hr hash rate becomes similar to the other machine
aikida3k
2018-10-13 13:58:08
How are you getting 100kh with nvme? I've only mined with mem in the past, setting up nvme mining now.
Shoots
2018-10-13 17:16:34
´>500k read IOPS´ on a low power unit which does not thermally throttle
Rotonen
2018-10-13 17:17:17
i try to keep an up to date skeleton for how to approach it
https://snowplough.kekku.li/wizard/nvme/ A quickstart wizard to help you get started with mining Snowblossom.
Rotonen
2018-10-13 18:12:57
@Rotonen I'll look but this isn't my first rodeo. However a timeout and reconnect might be long enough to trigger a work stop as the existing work unit would be considered stale.
Fireduck