3 ms·
Requests aren't made equal. I don't have an opinion about the manga hosting site, but I have worked on a website where many read requests required a lot of heav
by golergka 5y ago
Requests aren't made equal. I don't have an opinion about the manga hosting site, but I have worked on a website where many read requests required a lot of heavy joins other data work for actual useful work and weren't really cacheable, as every used requested his own data. Here's an example: https://cs.fastcup.net/match6279498/stats https://cs.fastcup.net/match6279498/stats
- jiggawatts 5y agoManga hosting is the poster child for slowly-changing, largely read only static content. A bunch of thumbnails and some text, with a basic search function. The site you linked is more interesting. It's the type of thing where the obvious optimisation would be to perform the complex processing in-memory for live games, and then return a single precomputed static document blob for old games. (I assume the match results don't change over time.) Most sites have data that isn't anywhere near as "live" as the developers assume it is...
- golergka 5y ago> I assume the match results don't change over time. In this example of one match they don't, but there's a lot of aggregates that are functions of live data.