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
Memory usage #48
Comments
Note :
I see no change to the memory behaviour Thanks Conor |
Hello @cgrantcal,
Note that you have to rebuild Please let me know how is your progress. Regards, |
@cgrantcal I've added a fix for disabling pool allocations. See #49. So to build oatpp with $ cd build/
$ cmake -DOATPP_DISABLE_POOL_ALLOCATIONS=ON ..
$ make
$ make install To make sure that oatpp is built with the right options you may add a log So now it should deallocate more memory once load is dropped and connections are closed. Please let me know if you have more questions. Best Regards, |
Hey @cgrantcal , Looks like not all pools are disabled. I think it might be a bug. Can you please specify what load you are running against your service:
Thanks, |
Hey, I am making simple post and get requests. Hope that helps. Thanks Conor |
Hey @cgrantcal , I've conducted some tests and results are as follows: Currently the best results in terms of memory you are able to get with oatpp being built as:
In this setup I get:
Also memory consumption will grow a bit as the load repeated till some point (due to memory fragmentation). I'll try to make some memory optimization in future, but for now it is what it is Best Regards, |
Hey,
I am running some tests and i notice that with more requests more memory is allocated as is expected. However i see that this memory is never de-allocated.
My question is that is there was a way for this memory to be de-allocated once the requests have been serviced and queuing reduced. I appreciate that this would not be the best for optimal performance. The host this is running on has limited resources, having a way to limit memory usage during low traffic periods would be helpful.
Any ideas you think could help are appreciated.
Regards
Conor
The text was updated successfully, but these errors were encountered: