-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature: Keep the memory usage of the service at a stable level #1216
Conversation
…rge body from slowly stretching the memory of the entire service
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also wondering, why can't you call Request.ReleaseBody()
or Response.ReleaseBody()
yourself?
Because fasthttp is well developed and there are many other supporting respositories available. For a business project, we want to configure the limit of request and response uniformly, so that the upper limit of the mem of the request response can be handled from a macro perspective, instead of repeating the coding in each place for recycling the critical value. |
|
Co-authored-by: Erik Dubbelboer <erik@dubbelboer.com>
Co-authored-by: Erik Dubbelboer <erik@dubbelboer.com>
Co-authored-by: Erik Dubbelboer <erik@dubbelboer.com>
Co-authored-by: Erik Dubbelboer <erik@dubbelboer.com>
Co-authored-by: Erik Dubbelboer <erik@dubbelboer.com>
Thanks! |
My pleasure |
add request and response body size limit, it prevents the large body from slowly stretching the memory of the entire service