Ping to EU server

[-MaVerick-]

Hello dearest prohashers,

I usually use the normal prohashing server when connecting my miners with a ping between 120-140ms, but with me sitting in Germany and the EU server also sitting in Germany afaik, I thought why not try it out. To my suprise the ping was worse instead of better, going up to 240ms. 99% of german servers are located in or around Frankfurt and I usually don't have any connection problems to there, I pretty much can drive to there.

Is there something I'm missing here? Or does the ping even matter that much in the end?

[jreysack]

latency matters quite a bit for submitting shares. less sub optimal shares

[Sarah Manter]

Hello dearest prohashers,

I usually use the normal prohashing server when connecting my miners with a ping between 120-140ms, but with me sitting in Germany and the EU server also sitting in Germany afaik, I thought why not try it out. To my suprise the ping was worse instead of better, going up to 240ms. 99% of german servers are located in or around Frankfurt and I usually don't have any connection problems to there, I pretty much can drive to there.

Is there something I'm missing here? Or does the ping even matter that much in the end?

Hey MaVerick! Would you be willing to test out our new EU sever for a bit today? It's not officially out yet, but we need a couple people to test it, and it would be interesting to know if it works better for you than the existing one.

[-MaVerick-]

My pleasure, I'll keep you updated.

[Sarah Manter]

My pleasure, I'll keep you updated.

Thank you. We do know that KAWPOW currently has an issue on the eu server starting with the 14th share that we're currently investigating, so if you're able to test one of the other algorithms, that would be great.

[-MaVerick-]

I did some testing with ETHPOW & Ghostrider. The EU server is still bad for me, I cannot make out any difference to the better. US server averages somewhere between 130-150ms, the best I can get is 180ms on EU with an average around 200ms and some heavy spikes up to 10.000ms.

My provider is pretty known for routing shenanigans, even forcing me to use a VPN for one MMO out there. So I guess thats more of a problem on my end, not server side.

[Steve Sokolowski]

Have you tried doing a traceroute to figure out where the data is actually going? You can find out which computers the packets travel through and how quickly each of them responds.

Try it for both us.mining.prohashing.com and eu.mining.prohashing.com and tell me what you see. I'm curious to find out whether this is indeed a routing problem, or whether there could be a configuration issue that we can actually improve.

[thundergun]

How do you test your ping from miners to prohashing servers?

[-MaVerick-]

US ->

Code: Select all

  1    <1 ms    <1 ms    <1 ms  speedport.ip [192.168.2.1]
  2     6 ms     5 ms     5 ms  p3e9bf40a.dip0.t-ipconnect.de [62.155.244.10]
  3    90 ms    89 ms    89 ms  nyc-sb6-i.NYC.US.NET.DTAG.DE [62.154.5.202]
  4    86 ms    86 ms    86 ms  be-200-pe11.60hudson.ny.ibone.comcast.net [173.167.56.189]
  5    89 ms    89 ms    89 ms  be-4311-cs03.newyork.ny.ibone.comcast.net [96.110.34.57]
  6    97 ms    97 ms    96 ms  96.110.42.26
  7   103 ms   102 ms   103 ms  be-33-ar01.lowerpaxton.pa.pitt.comcast.net [69.139.168.186]
  8   113 ms   113 ms   113 ms  162.151.48.102
  9   112 ms   112 ms   112 ms  be-2-sur03.statecollege.pa.pitt.comcast.net [162.151.20.66]
 10   112 ms   112 ms   111 ms  prohashing.com [50.220.121.209]

EU (new) ->

Code: Select all

  1    <1 ms    <1 ms    <1 ms  speedport.ip [192.168.2.1]
  2     8 ms     5 ms     8 ms  p3e9bf40a.dip0.t-ipconnect.de [62.155.244.10]
  3     8 ms     8 ms     9 ms  d-ed5-i.D.DE.NET.DTAG.DE [62.154.4.170]
  4     9 ms     8 ms     8 ms  d-ed5-i.D.DE.NET.DTAG.DE [62.154.4.170]
  5    44 ms    51 ms    22 ms  4.68.71.113
  6    11 ms    11 ms    10 ms  ae2.3222.edge9.Frankfurt1.level3.net [4.69.167.118]
  7    11 ms    10 ms    10 ms  fra-eq5-01gw.voxility.net [62.67.68.131]
  8    12 ms    13 ms    12 ms  fra-eq5-02gw.voxility.net [5.254.68.198]
  9    25 ms    24 ms    24 ms  vie-in1-01gw.voxility.net [93.115.89.10]
 10    39 ms    44 ms     *     buc-ird-01gw.voxility.net [5.254.80.18]
 11     *      826 ms     *     buc-ird-01c.voxility.net [109.163.235.58]
 12    37 ms    37 ms    37 ms  109.163.232.58
 13    41 ms    40 ms    43 ms  5.254.118.139

Hops 10&11 are giving me trouble.

[Sarah Manter]

US ->

Code: Select all

  1    <1 ms    <1 ms    <1 ms  speedport.ip [192.168.2.1]
  2     6 ms     5 ms     5 ms  p3e9bf40a.dip0.t-ipconnect.de [62.155.244.10]
  3    90 ms    89 ms    89 ms  nyc-sb6-i.NYC.US.NET.DTAG.DE [62.154.5.202]
  4    86 ms    86 ms    86 ms  be-200-pe11.60hudson.ny.ibone.comcast.net [173.167.56.189]
  5    89 ms    89 ms    89 ms  be-4311-cs03.newyork.ny.ibone.comcast.net [96.110.34.57]
  6    97 ms    97 ms    96 ms  96.110.42.26
  7   103 ms   102 ms   103 ms  be-33-ar01.lowerpaxton.pa.pitt.comcast.net [69.139.168.186]
  8   113 ms   113 ms   113 ms  162.151.48.102
  9   112 ms   112 ms   112 ms  be-2-sur03.statecollege.pa.pitt.comcast.net [162.151.20.66]
 10   112 ms   112 ms   111 ms  prohashing.com [50.220.121.209]

EU (new) ->

Code: Select all

  1    <1 ms    <1 ms    <1 ms  speedport.ip [192.168.2.1]
  2     8 ms     5 ms     8 ms  p3e9bf40a.dip0.t-ipconnect.de [62.155.244.10]
  3     8 ms     8 ms     9 ms  d-ed5-i.D.DE.NET.DTAG.DE [62.154.4.170]
  4     9 ms     8 ms     8 ms  d-ed5-i.D.DE.NET.DTAG.DE [62.154.4.170]
  5    44 ms    51 ms    22 ms  4.68.71.113
  6    11 ms    11 ms    10 ms  ae2.3222.edge9.Frankfurt1.level3.net [4.69.167.118]
  7    11 ms    10 ms    10 ms  fra-eq5-01gw.voxility.net [62.67.68.131]
  8    12 ms    13 ms    12 ms  fra-eq5-02gw.voxility.net [5.254.68.198]
  9    25 ms    24 ms    24 ms  vie-in1-01gw.voxility.net [93.115.89.10]
 10    39 ms    44 ms     *     buc-ird-01gw.voxility.net [5.254.80.18]
 11     *      826 ms     *     buc-ird-01c.voxility.net [109.163.235.58]
 12    37 ms    37 ms    37 ms  109.163.232.58
 13    41 ms    40 ms    43 ms  5.254.118.139

Hops 10&11 are giving me trouble.

Thank you. I've passed this along. At the moment, they have both eu.prohashing.com and eu.mining.prohashing.com pointing to the old eu server. Anyone with their config switched over to eu.mining.prohashing.com will be automatically be pointed toward the new server once we've made the fixes/changes we need to make before we officially go live with it.