News for hackers. Stuff that matters.

A comment on Before Reddit and Digg, there was Fark. Then a user-hostile redesign killed it. Parent comment

Re:Before Reddit and Digg, there was Fark. Then a user-hosti... by goykasi on Monday June 12, 2023 @05:28AM (#36290638)
How is reddit highly cacheable? Maybe old/infrequently accessed discussions are cacheable, but the live set is too dynamic. So there probably isnt much of a win there.

The feeds are definitely not cacheable (except for maybe on a per user basis with a low ttl). Popular and all are never the same upon reload. And every user is going to have a different combination of subreddits. Those feeds have to be generated on the fly. Most of the data is too dynamic and ever-changing to cache effectively.

[ Parent | on HN ]
Re:Before Reddit and Digg, there was Fark. Then a user-hosti... by conradfr on Monday June 12, 2023 @06:25AM (#36291182)
https://medium.com/@sevebadajoz/exploring-cache-optimization...

Also a lot of their content is not "hot" and "commentable" anymore.

[ Parent | on HN ]
Re:Before Reddit and Digg, there was Fark. Then a user-hosti... by raverbashing on Monday June 12, 2023 @07:20AM (#36291695)
- Cache for unlogged users, have a less dynamic front page (let's say 10s cache), that would help a lot

- Cache of most popular topics (again, even a 10s invalidation time) would help

For the logged users you could do something more dynamic, for example, cache the front-page snippets of the main subs + add the ones for the user. And again cache that

(unless the 'new reddit' makes this harder, to which I would say - well deserved! ;) )

[ Parent | on HN ]