H2O
Infrastructure
web server
SHOW HN2015
How HN took it
0 positive, 3 neutral or asking, 0 mixed, 2 critical, out of 5 comments about the project. Thread score -0.26.
Performance: 0 for, 2 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful tool for real-world speed evaluation (PageSpeed/WebPageTest suggestion)
From 1 comment
Thank you for the suggestion. In case of the benchmark, I run the server as a VM instance on the client machine so that the results would be reproducible (with network latency…
kazuho on HN
Objections
Single runs may be too noisy for reliable timing data
From 1 comment
Are your timings based off of a single run each for Firefox and Chrome? The web is a very noisy place; to get good timing data you need to run many tests. WebPageTest…
cbr on HN
Chrome timings include a 0.2s block that was subtracted, making charts hard to compare
From 2 comments
I'm not sure I'm reaching the same conclusion. - Chrome is taking 618ms to load / vs 412 ms on FF. - FF loads all the .css & .js at 320ms as well as first 8 imgs - CH loads all…
burgreblast on HNThanks, I missed that. Might be worth re-running the tests without the block so the graphs can line up better and we don't need to subtract the 200ms? As you well know,…
burgreblast on HN
Initial HTML latency remains before dependent resources are requested
From 1 comment
Seems like there is still a significant amount of initial latency by waiting for the first-byte of the HTML before making the subsequent requests for the dependent resources. To…
supertruth on HN
Requests
Rerun tests without subtracting the Chrome connection block
From 1 comment
Thanks, I missed that. Might be worth re-running the tests without the block so the graphs can line up better and we don't need to subtract the 200ms? As you well know,…
burgreblast on HN
Test with many runs and real-world conditions like WebPageTest
From 1 comment
Are your timings based off of a single run each for Firefox and Chrome? The web is a very noisy place; to get good timing data you need to run many tests. WebPageTest…
cbr on HN
Questions
Does HTTP/2 allow server to send dependent resources eagerly?
From 1 comment
Seems like there is still a significant amount of initial latency by waiting for the first-byte of the HTML before making the subsequent requests for the dependent resources. To…
supertruth on HN
Why is fetching the root page slower on Chrome than Firefox?
From 1 comment
I'm not sure I'm reaching the same conclusion. - Chrome is taking 618ms to load / vs 412 ms on FF. - FF loads all the .css & .js at 320ms as well as first 8 imgs - CH loads all…
burgreblast on HN
Alternatives named
WebPageTest
From 1 comment
Are your timings based off of a single run each for Firefox and Chrome? The web is a very noisy place; to get good timing data you need to run many tests. WebPageTest…
cbr on HN
PageSpeed
From 1 comment
Are your timings based off of a single run each for Firefox and Chrome? The web is a very noisy place; to get good timing data you need to run many tests. WebPageTest…
cbr on HN