6 ms·
Very zippy indeed! Have you thought about switching to nginx so you can get SPDY (and soon HTTP/2)? Also, Hugo is cool. I've evaluated it myself, but I have 8 y
by aorth 11y ago
Very zippy indeed! Have you thought about switching to nginx so you can get SPDY (and soon HTTP/2)? Also, Hugo is cool. I've evaluated it myself, but I have 8 years of WordPress archives -- ~500 posts -- and I worry about things like images, comments, etc.
- dimitar 11y agoI would try to use the Jekyll WordPress import tool to get the markdown files.
- kmfrk 11y agoDoing an import is hardly going to ruin your existing installation. Back up your blog and do the Jekyll import, and see if it’s worth switching to you. :)
- aorth 11y agoIndeed! It is rather a limit on time. :P
- kmfrk 11y agoI actually don’t know how fast Jekyll builds blog posts nowadays, but it has been a little on the slow side at one point. No idea how it’d handle 500 blog posts - but there’s only one way of finding out!
- jacquesm 11y agoNo idea either but for when you do here is the Hugo breakdown: 302 pages created 267 categories created gin 1149 ms real 0m1.613s user 0m1.180s sys 0m0.408s
- jacquesm 11y agoThe benefits from SPDY are probably not going to help much if you only do one request :)
- chrismorgan 11y agoThings like resource inlining are an antipattern in an HTTP/2 world. The stylesheet for example should not be inlined; the server should instead push the stylesheet out to the user agent proactively (typically three frames—a PUSH_PROMISE telling the client of the request that is being simulated, then a HEADERS and a DATA frame with the response). The first time, the browser will receive it approximately as fast as the inlined version; subsequent times, there is no overhead, moreover browsers can load the stylesheet only once rather than needing to load it for every page.
- xorcist 11y agoApache has support for HTTP/2 today. A switch to nginx would mean to wait until they launch support later this year.