Re:300ms Faster: Reducing Wikipedia's Total Blocking Time
by robin_reala on Monday May 29, 2023 @10:49AM
(#36114540)
This is fairly typical, and applies to HN too – you’ll see dang suggesting that people log out when there’s breaking news that gets a lot of engagement here.
[ Parent
| on HN ]
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time
by remram on Monday May 29, 2023 @11:12AM
(#36114759)
The difference is that HN stays very fast. Being logged in is more costly for the backend, but doesn't degrade your experience as a user. On Wikipedia you really suffer for being logged in.
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time
by electroly on Monday May 29, 2023 @01:24PM
(#36115958)
When HN is slammed, you just get the "sorry, HN is having problems" message. This is when dang suggests logging out. On many occasions that turns not being able to see the site at all into the site working quickly.
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time
by remram on Monday May 29, 2023 @07:00PM
(#36119119)
Sure, past some threshold HN goes down, and at that point there is a (big) difference between the logged-in and logged-out experience. My point is that, the rest of the time, there is not, whereas for Wikipedia, the logged-in experience is always significantly worse than the logged-out experience. This encourages people to not log in which is a problem.