OF
Hello Hardpick,
how important is ping time?
I am getting 360 mh/s from 2nd batch icarus on deepbit which has a ping time of 410 ms
(my isp ping time is 11ms -- have adsl2 at 12.34 mbps/ 0.83 mbps -- I live in sydney australia)
I have tested other pools
...
ecki.net.-----361ms
...
361 ms from Australia to Thailand? This is very bad...
Which Internet Provider do you use? Telstra?
I have
less than 200ms to my customers in Sydney from here (Thailand)... so it is the same distance!
Antwort von 203.37.115.162: Bytes=32 Zeit=189ms TTL=236
Antwort von 203.37.115.162: Bytes=32 Zeit=190ms TTL=236
Antwort von 203.37.115.162: Bytes=32 Zeit=188ms TTL=236
Antwort von 203.37.115.162: Bytes=32 Zeit=184ms TTL=236
Ping-Statistik für 203.37.115.162:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 184ms, Maximum = 190ms, Mittelwert = 187msCould you PM me your traceroute to
miner.ecki.net please?
Note:
NOT ecki.net, because this will be in Germany and not Thailand where the pool server is located!
The ping time is important, but the variance is also very important.
The difference between Minimum, Maximum and Average should be as little as possible!
But most important for mining are the number of packet drops!So just ping the target 10000 times and have a look about the % of packet losses.
Ping is important, but it is not all...
If you have a high number of packet drops to your current pool, then choose another one and it will increase your current hash rate of 360 MH/s!For more answers or information about network questions please PM me, this is off topic here in this thread
(I assume)... even you are using an Icarus board.
Cu,
Ecki
Hi Ecki
Thanks for the help
I have changed to queued mining and now get 380 mh/sec --
only problem that need to be resolved is miner lockup (I am in process of changing PC - if this does not resolve problem will then try other pools)
I no longer think ping time is a problem unless it is causing the lockup
below is the info
Tracing route to miner.ecki.net [110.77.137.88]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192-168-100-1.tpgi.com.au [192.168.100.1]
2 <1 ms <1 ms <1 ms donduck.gateway [192.168.0.1]
3 19 ms 20 ms 19 ms xx.xx.xx.xxx (hiden by me ie my ip)
4 20 ms 20 ms 20 ms 202.7.173.149
5 20 ms 19 ms 19 ms syd-sot-ken-crt2-ge-6-0-0.tpgi.com.au [202.7.171.105]
6 19 ms 20 ms 19 ms syd-sot-ken-crt-4-Ten-9-1.tpgi.com.au [203.29.135.157]
7 20 ms 19 ms 19 ms syd-sot-ken-crt-4-Ten-9-1.tpgi.com.au [203.29.135.157]
8 120 ms 120 ms 120 ms ix-11-1-0-507.tcore2.TV2-Tokyo.as6453.net [116.0.88.21]
9 188 ms 188 ms 212 ms if-6-2.tcore1.SVW-Singapore.as6453.net [180.87.12.109]
10 203 ms 204 ms 204 ms if-12-0-0.core1.SVQ-Singapore.as6453.net [180.87.36.21]
11 203 ms 210 ms 216 ms Vlan1107.icore1.SVQ-Singapore.as6453.net [120.29.214.2]
12 193 ms 197 ms 194 ms Vlan563.icore1.SVQ-Singapore.as6453.net [120.29.215.78]
13 232 ms 232 ms 232 ms 61.19.9.149
14 217 ms 216 ms 221 ms 61.19.9.29
15 222 ms 222 ms 222 ms 61.19.9.34
16 232 ms 232 ms 234 ms 61.19.15.186
17 217 ms 218 ms 216 ms 110.77.255.38
18 236 ms 238 ms 236 ms 110.77.252.142
19 265 ms 281 ms 310 ms mail2.ecki.net [110.77.137.88]
Trace complete.
ping test below to miner.ecki.net ---- 1000 times
Pinging miner.ecki.net [110.77.137.88] with 32 bytes of data:
Reply from 110.77.137.88: bytes=32 time=372ms TTL=49
Reply from 110.77.137.88: bytes=32 time=290ms TTL=49
Ping statistics for 110.77.137.88:
Packets: Sent = 1000, Received = 986, Lost = 14 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 241ms, Maximum = 566ms, Average = 307ms
ping test to deepbit below 10,000 times
Pinging deepbit.net [46.4.121.118] with 32 bytes of data:
Reply from 46.4.121.118: bytes=32 time=411ms TTL=44
Reply from 46.4.121.118: bytes=32 time=411ms TTL=44
Ping statistics for 46.4.121.118:
Packets: Sent = 10000, Received = 10000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 409ms, Maximum = 637ms, Average = 410ms
my intenet provider is tpg.com.au
regards
Luke