6 ms·
"and part of it is the backend is really really really resource hungry." hmmm ... we are serving our topic pages in 83ms median in 6 hours I can count 4 times
by sams99 13y ago
"and part of it is the backend is really really really resource hungry."
hmmm ... we are serving our topic pages in 83ms median in 6 hours I can count 4 times it took us a second to serve a topic page. This is across MANY sites.
so I am sorry going to have to call bullshit on perf issues caused by server perf. Server perf is fine.
Client perf can improve and we are constantly working on improving it.
That said:
http://www.webpagetest.org/result/140320_HJ_923/ http://www.webpagetest.org/result/140320_HJ_923/
First view 3.255
Repeat view 2.075
Is pretty good, and it is actually faster than that when navigating between pages.
- maxerickson 13y agoThe comparison is vaguely obnoxious, but HN is in the browser rendering before the first byte is returned from Discourse: http://www.webpagetest.org/result/140320_K8_MJF/ http://www.webpagetest.org/result/140320_K8_MJF/ I realize they are different systems with different goals (and different users and...), but the spare interface here does come with some benefits.
- sams99 13y agoMy blog runs Discourse as the backend http://www.webpagetest.org/result/140320_55_XPN/ http://www.webpagetest.org/result/140320_55_XPN/ just sayin...
- maxerickson 13y agoI thought the more interesting part of the comparison was as a point of reference for the qualitative evaluation of 'fast enough'. Discourse is a lot more feature rich than HN, so the actual difference in terms of numbers isn't real useful, but HN at 0.7 seconds or whatever still doesn't feel ultra snappy.
- voltagex_ 13y agoSorry, yes. I was mixing up a few things in my head.