our caching strategy is a lot more disconcerting now that people make requests directly on the site

very-scary-scenario / nkd.su

A Neko Desu request robot.

https://nkd.su

Other

4 stars 2 forks source link

our caching strategy is a lot more disconcerting now that people make requests directly on the site #250

Open colons opened 1 year ago

colons commented 1 year ago

it made sense to have fairly lethargic caching when requests were only ingested every couple of minutes and from a different website. now that people are doing it here, it's probably reasonable for them to expect stuff to show up immediately

colons commented 1 year ago

the worst of this was on user pages, and 158fe40b20aa8b24ce98f688d2dff98e910e64f4 mitigated this i think completely. the front page still needs work here; in particular, it should respond quickly when:

a new request is added
a track is played

the whole cache setup probably needs examining; it hasn't been really rethought in a long time. perhaps a lot of it could be removed entirely by making database queries more efficient?