Matchu
18bc3df6f4
I tried running a pressure test against assetImage on prod with the open-source tool `wrk`: ``` wrk -t12 -c20 -d20s --timeout 20s 'https://impress-2020-box.openneo.net/api/assetImage?libraryUrl=https%3A%2F%2Fimages.neopets.com%2Fcp%2Fitems%2Fdata%2F000%2F000%2F522%2F522756_2bde0443ae%2F522756.js&size=600' ``` I found that, unsurprisingly, we run a lot of concurrent requests, which fill up memory with a lot of Chromium instances! In this change, we declare a small pool of 2 browser contexts, to allow a bit of concurrency but still very strictly limit how many browser instances can actually get created. We might tune this number depending on the actual performance characteristics! |
||
|---|---|---|
| .. | ||
| allWakaValues.js | ||
| assetImage.js | ||
| graphql.js | ||
| outfitImage.js | ||
| sendFeedback.js | ||
| uploadLayerImage.js | ||
| validPetPoses.js | ||