<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Youden</author><text>You might know this but in case others don&amp;#x27;t, seeing different speed test results to different services&amp;#x2F;servers is completely normal.&lt;p&gt;A lot of people forget or don&amp;#x27;t understand the &amp;quot;net&amp;quot; part of &amp;quot;internet&amp;quot;. The internet isn&amp;#x27;t a monolithic service you connect to. When your ISP offers you &amp;quot;1Gbps&amp;quot; internet, they&amp;#x27;re not guaranteeing that whatever your activity, you will get 1Gbps, they&amp;#x27;re just giving you a 1Gbps connection to their network.&lt;p&gt;Their network will then interconnect with other networks. Depending on the specifics of those interconnections, you will see different performance characteristics depending on what you&amp;#x27;re doing.&lt;p&gt;For example my ISP peers with a particular network that hosts servers ~600km away that I exchange a ton of data with. I get 1Gbps when I use my ISP. However when I use a different local ISP that doesn&amp;#x27;t peer with the remote network, I see significantly reduced speeds, because the route taken to exchange data isn&amp;#x27;t optimal.&lt;p&gt;I know the HN crowd is fairly technically competent but I&amp;#x27;ve seen plenty of competent people who I think knew this in an abstract sense but it just hadn&amp;#x27;t clicked for them what the practical consequences were.</text><parent_chain><item><author>js2</author><text>Cloudflare: 455 Mbps down &amp;#x2F; 73.1 Mbps up &amp;#x2F; Latency 13.0 ms &amp;#x2F; Jitter 2.26 ms &amp;#x2F; Server: Ashburn via IPv6.&lt;p&gt;Netflix (fast.com): 790 Mbps down &amp;#x2F; 950 Mbps up &amp;#x2F; Latency 8 ms unloaded, 12 ms loaded &amp;#x2F; Server: Ashburn via IPv6.&lt;p&gt;Ookla (speedtest.net): 928 Mbps down &amp;#x2F; 938 Mbps up &amp;#x2F; Ping 1 ms &amp;#x2F; Server: Raleigh via IPv4.&lt;p&gt;DSL Reports (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.dslreports.com&amp;#x2F;speedtest&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.dslreports.com&amp;#x2F;speedtest&lt;/a&gt;): 611 Mbps down &amp;#x2F; 929 Mbps up &amp;#x2F; ping 16-41ms &amp;#x2F; Servers: Houston, Dallas, Newcastle DE, Nashville TN, Dallas.&lt;p&gt;Location: Raleigh. Provider: AT&amp;amp;T fiber.&lt;p&gt;Test run using Safari, macOS 10.15.4, Thunderbolt Ethernet.&lt;p&gt;Edit: the small file sizes used for some of the tests seem to drag down the overall speed measurement quite a bit. It&amp;#x27;s biased against upload measurements too since there&amp;#x27;s download files sizes of 25MB and 100MB whereas upload tests only up to 10MB file size. But even there, something seems off. The upload measurements are much smaller for the same file sizes (e.g. 170 Mbps avg vs 7 Mbs average for a 10 kB file).&lt;p&gt;I question this methodology. I care most about my 1Gps when I&amp;#x27;m downloading the latest version of Xcode or some other huge file. I guess the smaller sizes are to better emulate downloading web pages, but in that case, the latency is probably what matters more. Even with 1Gps, when I&amp;#x27;m out in CA, sites typically feel faster.&lt;p&gt;Edit 2:&lt;p&gt;speedtest.googlefiber.net: 800-900 Mbps down &amp;#x2F; 800-900 Mbps up (multiple tests to servers in Charlotte, Raleigh, Atlanta, seems to bounce around each time I reload the page).&lt;p&gt;Speedtest (Ookla) with server manually set to Windstream in Ashburn, VA: 886 Mbps down, 900 Mbps up. Confirmed that my router is measuring the same amount, so Ookla isn&amp;#x27;t just making up these numbers.</text></item></parent_chain></comment><story><title>Speed.cloudflare.com</title><url>https://speed.cloudflare.com/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>leihca</author><text>Thanks for the feedback, very much appreciated! I&amp;#x27;m a product manager here at Cloudflare, responsible for launching this tool. Since the launch, we&amp;#x27;ve found some issues that we&amp;#x27;re going to address:&lt;p&gt;- Especially for users with a very fast Internet connection, speed.cloudflare.com reports upload speeds much lower than expected figures. We don&amp;#x27;t yet know what is causing this but will disable the upload part of the test until we know more.&lt;p&gt;- In general reported download speeds are little lower than figures coming from other speed tests. We will revisit our methodology to understand the discrepancy.&lt;p&gt;- Re: the speed test automatically starting: we appreciate the feedback and understand why some users may not want this as default behavior. We will disable the auto-start for now.&lt;p&gt;In the meantime, we appreciate any and all feedback, please keep it coming: you can reach me at achiel [at] cloudflare.com</text><parent_chain><item><author>js2</author><text>Cloudflare: 455 Mbps down &amp;#x2F; 73.1 Mbps up &amp;#x2F; Latency 13.0 ms &amp;#x2F; Jitter 2.26 ms &amp;#x2F; Server: Ashburn via IPv6.&lt;p&gt;Netflix (fast.com): 790 Mbps down &amp;#x2F; 950 Mbps up &amp;#x2F; Latency 8 ms unloaded, 12 ms loaded &amp;#x2F; Server: Ashburn via IPv6.&lt;p&gt;Ookla (speedtest.net): 928 Mbps down &amp;#x2F; 938 Mbps up &amp;#x2F; Ping 1 ms &amp;#x2F; Server: Raleigh via IPv4.&lt;p&gt;DSL Reports (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.dslreports.com&amp;#x2F;speedtest&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.dslreports.com&amp;#x2F;speedtest&lt;/a&gt;): 611 Mbps down &amp;#x2F; 929 Mbps up &amp;#x2F; ping 16-41ms &amp;#x2F; Servers: Houston, Dallas, Newcastle DE, Nashville TN, Dallas.&lt;p&gt;Location: Raleigh. Provider: AT&amp;amp;T fiber.&lt;p&gt;Test run using Safari, macOS 10.15.4, Thunderbolt Ethernet.&lt;p&gt;Edit: the small file sizes used for some of the tests seem to drag down the overall speed measurement quite a bit. It&amp;#x27;s biased against upload measurements too since there&amp;#x27;s download files sizes of 25MB and 100MB whereas upload tests only up to 10MB file size. But even there, something seems off. The upload measurements are much smaller for the same file sizes (e.g. 170 Mbps avg vs 7 Mbs average for a 10 kB file).&lt;p&gt;I question this methodology. I care most about my 1Gps when I&amp;#x27;m downloading the latest version of Xcode or some other huge file. I guess the smaller sizes are to better emulate downloading web pages, but in that case, the latency is probably what matters more. Even with 1Gps, when I&amp;#x27;m out in CA, sites typically feel faster.&lt;p&gt;Edit 2:&lt;p&gt;speedtest.googlefiber.net: 800-900 Mbps down &amp;#x2F; 800-900 Mbps up (multiple tests to servers in Charlotte, Raleigh, Atlanta, seems to bounce around each time I reload the page).&lt;p&gt;Speedtest (Ookla) with server manually set to Windstream in Ashburn, VA: 886 Mbps down, 900 Mbps up. Confirmed that my router is measuring the same amount, so Ookla isn&amp;#x27;t just making up these numbers.</text></item></parent_chain></comment><story><title>Speed.cloudflare.com</title><url>https://speed.cloudflare.com/</url></story>