1
0
Fork 0
forked from OpenNeo/impress
impress/src/server
Matchu a3423cd6d6 cache asset manifests in the db
Here's just some simple caching: we try to load the asset manifest from the db with the rest of the asset. If it's not present, we load it via HTTP, and write it to the database.

I might try to do a bulk write of manifests at some point, too.

This is because I noticed that one of the main bottlenecks in most of the endpoints now (and definitely the highest-variance) was loading from images.neopets.com.

Another approach I considered was HTTP/2 to load the manifests, because it kinda looks like the server is refusing to open all these sockets at once and effectively does the requests in waves? But images.neopets.com doesn't support HTTP/2 right now anyway, so oh well! (And that would have probably cut us down to ~250ms of HTTP time still, instead of ~600–700. Also, why is network out of Vercel so slow? :p)
2020-08-17 17:50:01 -07:00
..
__snapshots__ update test snapshots 2020-08-09 23:03:53 -07:00
lib some Honeycomb fixes 2020-08-17 01:16:35 -07:00
query-tests cache zone data 2020-08-17 15:28:05 -07:00
db.js add Honeycomb logging 2020-08-16 23:28:41 -07:00
getValidPetPoses.js transition to closest valid pose for species/color 2020-05-23 13:23:24 -07:00
getValidPetPoses.test.js refactor e/gp pairs to pose enum 2020-05-23 12:47:06 -07:00
index.js cache asset manifests in the db 2020-08-17 17:50:01 -07:00
loaders.js cache zone data 2020-08-17 15:28:05 -07:00
neopets.js use PetService to determine the correct pose 2020-05-23 13:55:59 -07:00
util.js use PetService to determine the correct pose 2020-05-23 13:55:59 -07:00