Conversation
✅ Deploy Preview for imgproxy-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Hi @xiaofeige! I thought about something like this myself but decided not to do so and there are several reasons for this:
|
yeah, you are right, but I think it's a trade-off. In my presure test, I noticed that there are much more memory left when CPU is 100% used. When I move the concurrency control to where I suggest, memory didn't grow that fast, basicly the same as before., but avg qps improved a lot. |
|
by the way, format & resize operation performance are very pool, do you known how to improve it by adjust the configuration? thanks a lot. ^_^ |
a870541 to
6e4967a
Compare
In my opinion, there is no need to wait for the IO complete. once the image caculation is done, the concurrency control strategy should let the request just go though, thus, making the CPU fully used.