News for hackers. Stuff that matters.
Re:Why HN was slow and how Rtm fixed it by aonic on Wednesday January 19, 2011 @04:57PM (#2121430)
Varnish supports edge side includes. The header bar could be an ESI and the rest of the page could be cached
Re:Why HN was slow and how Rtm fixed it by nuclear_eclipse on Wednesday January 19, 2011 @05:37PM (#2121555)
> and the rest of the page could be cached

Except they can't, for the reasons I mentioned above. Eg, if my account is deaded, when I view a thread with one of my own comments, it looks different than if someone else was viewing that some thread, especially for those of us with or without showdead checked in our profiles.

Its not as straightforward as you would like it to be.

Re:Why HN was slow and how Rtm fixed it by aonic on Wednesday January 19, 2011 @07:14PM (#2121915)
Special cookies could be set for dead users and users who enable showdead to bypass the cache.

For example, one of the sites I run has about 50K pageviews/day by logged in users, and another 600K pageviews/day by anonymous users coming from referrals or search engines. Logged in users have similar customization options so we bypass cache for these users by detecting a cookie.

Obviously going the cache route would require some changes to how things are setup, its not a turn-key solution. But the insignificant amount of changes are well worth it for most content sites, but for a user generated content site like HN it would also depend on how the TTLs and cache purging are setup.

Re:Why HN was slow and how Rtm fixed it by nitrogen on Wednesday January 19, 2011 @07:47PM (#2122019)
The majority of requests probably come from live accounts in good standing or from people not even logged in, so the majority of requests could still be cached.
Re:Why HN was slow and how Rtm fixed it by nkurz on Thursday January 20, 2011 @01:05AM (#2122860)
Interesting point: what percentage of viewers are logged in? I was presuming it was high, but I guess I really don't know.