Jump to content
boristofu

How to Test upload to Frankfurt/Amsterdam

Recommended Posts

Hello guys, I need to know my estimated upload to Frankfurt or Amsterdam for Streaming purposes. 

 

I can only choose Great Britain in servers.. everything else is outside EU. 

 

Thanks

 

I'm putting a machine online for you in Frankfurt DE.  Give me a few minutes.

Share this post


Link to post
Share on other sites

Here you go...

 

http://de.testmy.net/SmarTest/up (initiates an automatic upload test to Frankfurt DE)

http://de.testmy.net/SmarTest/down (initiates an automatic download test to Frankfurt DE)

 

You can manually change the size by using the following url format...

http://de.testmy.net/ul-1MB 

[or in kB] http://de.testmy.net/ul-1024

(download test urls)

http://de.testmy.net/dl-1MB or http://de.testmy.net/dl-1024

Hope this helps.  Keep in mind that I've only quickly added this for you, it will appear in the logs as London, GB until I really add it.  As long as it says de.testmy.net in the bowser while it's testing... you're testing to Deutschland.  I may integrate it later if the server proves worthy.

 

This is outside of my normal Softlayer network on Linode but it should serve your purpose.  Testing against the server wasn't totally ideal but that may have to do with the outbound peers leaving Germany.  I'd have to test within DE outside of the host network to know for sure.

 

This is downloading from the server.  de.testmy.net to eu.testmy.net

[[email protected] tmp]# wget http://de.testmy.net/dl-200MB
--2015-08-15 13:12:47--  http://de.testmy.net/dl-200MB
Resolving de.testmy.net... 85.90.245.112
Connecting to de.testmy.net|85.90.245.112|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “dl-200MB.1”

    [         <=>                           ] 209,793,956 14.0M/s   in 13s     

2015-08-15 13:13:01 (15.7 MB/s) - “dl-200MB.1” saved [209793956]

and then in the other direction, from eu.testmy.net to de.testmy.net

[[email protected] tmp]# wget http://eu.testmy.net/dl-200MB
--2015-08-15 18:05:35--  http://eu.testmy.net/dl-200MB
Resolving eu.testmy.net (eu.testmy.net)... 159.8.149.164
Connecting to eu.testmy.net (eu.testmy.net)|159.8.149.164|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘dl-200MB’

    [            <=>                 ] 209,793,956 90.5MB/s   in 2.2s   

2015-08-15 18:05:38 (90.5 MB/s) - ‘dl-200MB’ saved [209793956]

So uploading to the DE server is definitely not going to be an issue.  But coming out of the server, at least when going to my server in London, it's not as fast as I'd like to see.  Ideally I'd like to see at least 75-100 MB/s (600-800 Mbps) in both directions.

 

In testing out to dallas2.testmy.net both the EU and new DE servers performed well for me.

[[email protected] tmp]# wget http://dallas2.testmy.net/dl-200MB
--2015-08-15 13:17:47--  http://dallas2.testmy.net/dl-200MB
Resolving dallas2.testmy.net... 108.168.210.66
Connecting to dallas2.testmy.net|108.168.210.66|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “dl-200MB.2”

    [                      <=>           ] 209,793,960 57.8M/s   in 5.2s    

2015-08-15 13:17:53 (38.5 MB/s) - “dl-200MB.2” saved [209793960]
[[email protected] tmp]# wget http://dallas2.testmy.net/dl-200MB
--2015-08-15 18:15:36--  http://dallas2.testmy.net/dl-200MB
Resolving dallas2.testmy.net (dallas2.testmy.net)... 108.168.210.66
Connecting to dallas2.testmy.net (dallas2.testmy.net)|108.168.210.66|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘dl-200MB.2’

    [                 <=>         ] 209,793,960 53.3MB/s   in 7.6s   

2015-08-15 18:15:44 (26.2 MB/s) - ‘dl-200MB.2’ saved [209793960]

Testing de to dallas...

[email protected] [/tmp]# wget http://de.testmy.net/dl-200MB
--2015-08-15 11:20:20--  http://de.testmy.net/dl-200MB
Resolving de.testmy.net... 85.90.245.112
Connecting to de.testmy.net|85.90.245.112|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “dl-200MB”

    [            <=>         ] 209,793,956 14.2M/s   in 15s     

2015-08-15 11:20:36 (13.0 MB/s) - “dl-200MB” saved [209793956]

Not bad given the distance but again not what I really like to see from a test server.  Other routes to different people and different times of day may have better or worse results, I'm not sure yet.

 

In other words... it's ready for testing but you're the first to use it so let me know what you think of the results that come off it.

Share this post


Link to post
Share on other sites

Lenoir NC

--2015-08-15 14:46:12--  https://testmy.net/dl-200MB
Resolving testmy.net (testmy.net)... 75.126.52.197
Connecting to testmy.net (testmy.net)|75.126.52.197|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `dl-200MB'

    [                 <=>                   ] 209,794,377 61.7M/s   in 3.2s    

2015-08-15 14:46:16 (61.7 MB/s) - `dl-200MB' saved [209794377]

Share this post


Link to post
Share on other sites

 

Lenoir NC

--2015-08-15 14:46:12--  https://testmy.net/dl-200MB
Resolving testmy.net (testmy.net)... 75.126.52.197
Connecting to testmy.net (testmy.net)|75.126.52.197|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `dl-200MB'

    [                 <=>                   ] 209,794,377 61.7M/s   in 3.2s    

2015-08-15 14:46:16 (61.7 MB/s) - `dl-200MB' saved [209794377]

 

Very nice.  Do the same to de.testmy.net ... and then to uk.testmy.net.

Share this post


Link to post
Share on other sites

Have no idea how I left out the specific servers and never thought twice about the throughput  Oo 

--2015-08-15 15:22:56--  http://de.testmy.net/dl-200MB
Resolving de.testmy.net (de.testmy.net)... 85.90.245.112
Connecting to de.testmy.net (de.testmy.net)|85.90.245.112|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `dl-200MB.1'

    [                                       <=>              ] 209,793,958 13.9M/s   in 15s     

2015-08-15 15:23:12 (13.7 MB/s) - `dl-200MB.1' saved [209793958]


--2015-08-15 15:24:14--  http://uk.testmy.net/dl-200MB
Resolving uk.testmy.net (uk.testmy.net)... 159.8.149.164
Connecting to uk.testmy.net (uk.testmy.net)|159.8.149.164|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `dl-200MB.2'

    [                                       <=>              ] 209,793,958 31.8M/s   in 8.9s    

2015-08-15 15:24:24 (22.5 MB/s) - `dl-200MB.2' saved [209793958]

Share this post


Link to post
Share on other sites

With me, I get slightly quicker with the UK server (right) than the Frankfurt one (left):

 

CLASxIkP.png StKHhnsV.png

 

Then again, my fixed wireless ISP probably could do with a routing equivalent of a satnav update when it comes to routing - 23 hops to reach the UK server: :laugh:

 

post-248268-0-80886700-1439759891.png

 

If hop #19 is what I think it means, it looks like my connection to the UK Testmy server goes through Amsterdam! :huh:

 

Traceroute re-run with my DSL connection only takes half the hop count:

 

post-248268-0-39715400-1439760249.png

Share this post


Link to post
Share on other sites

Tracing route to de.testmy.net [85.90.245.112]
over a maximum of 30 hops:

  1     3 ms     8 ms     3 ms  192.168.0.1
  2    19 ms    17 ms    27 ms  cpe-74-132-0-1.kya.res.rr.com [74.132.0.1]
  3    27 ms    24 ms    17 ms  74.128.4.253
  4    20 ms    28 ms    21 ms  be24.lsvqkydb01r.midwest.rr.com [65.29.31.48]
  5    32 ms    32 ms    43 ms  be24.clevohek01r.midwest.rr.com [65.189.140.166]
  6    43 ms    44 ms    38 ms  bu-ether47.vinnva0510w-bcr00.tbone.rr.com [107.14.19.38]
  7    52 ms    65 ms    85 ms  bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
  8    47 ms    45 ms    38 ms  0.ae0.pr0.dca10.tbone.rr.com [66.109.6.183]
  9    38 ms    42 ms    38 ms  be3021.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
 10   118 ms   120 ms   118 ms  be2268.ccr42.par01.atlas.cogentco.com [154.54.28.110]
 11   134 ms   130 ms   127 ms  be2278.ccr42.fra03.atlas.cogentco.com [154.54.62.78]
 12   124 ms   133 ms   127 ms  be2502.rcr21.b015749-1.fra03.atlas.cogentco.com [154.54.39.182]
 13   127 ms   125 ms   127 ms  149.11.106.18
 14   129 ms   128 ms   126 ms  62.209.33.210
 15   140 ms   126 ms   127 ms  139.162.129.0
 16   178 ms   166 ms   271 ms  li1428-112.members.linode.com [85.90.245.112]

Trace complete.

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...
Speed Test Version 15.9
© 2019 TestMy Net LLC - TestMy.net - Terms & Privacy