Re: Memory bloat on concurrency - Any fix to release memory post query run

Hai Sreejith, There is no way to manually force MonetDB to release memory. However, what you described is not supposed to happen. Not very long ago (but should be before the version you use), we have put quite some efforts in release unused memory earlier (i.e. free a variable as soon as it’s not needed, instead of waiting until the end of query execution to release all variables at once) so as to reduce MonetDB’s virtual memory usage. Can you please upgrade to the latest release Jul2017-SP1 (11.27.5)? The version you’re using is a bit old. In the bug-fix releases following that, several memory leaks were fixed [1]. If your problem persists, can you please give us the necessary data sample, schema, queries and script to reproduce your problem? Regards, Jennie [1] https://www.monetdb.org/OldReleaseNotes/Dec2016

On 10 Aug 2017, at 11:26, Sharma, Sreejith wrote:

Hi,

I have been using monetdb (11.25.3) in CentOS for one of application. I have been working on a PSR testing for this application and have noticed on high concurrency and on same pattern of query running again and again causing memory to bloat up and doesn’t release once the query run completes. I understand that the data is lifted into memory and the result set is also cached, however I assume this should be release once the system is idle which I don’t see it as of now.

Is there any way or parameter to release the unused memory blocks? I have asked this before, but couldn't get to the root to fix this.

Regards, Sreejith _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list