Hello Sreejith, A memory dump is not going to be of much help in this case. A better direction for your investigation is to look into MonetDB’s query execution trace. It tells you which relational operator is executed, for how long, and how much memory it consumes. There are several tools for this. Please have a look at stethoscope: https://www.monetdb.org/Documentation/Manuals/MonetDB/Profiler/Stethoscope, and tomograph: https://www.monetdb.org/Documentation/Manuals/MonetDB/Profiler/tomograph MonetDB is very memory eager. It will keep allocating more memory until it decides that a variable is no longer use (which will then be free-ed). So, growing memory consumption doesn’t necessarily mean memory leaks. Although, you can check for memory leaks using tools such as valgrind. Hope this helps, Jennie

On 22 Aug 2017, at 18:40, Sharma, Sreejith wrote:

Anyone has any thoughts on below?

AM using below MonetDB version –

MonetDB Database Server Toolkit v1.1 (Dec2016-SP5) MonetDB 5 server v11.25.23 "Dec2016-SP5" (64-bit, 128-bit integers) OS - CentOS

From: users-list [mailto:users-list-bounces+sreejith.sharma=harman.com@monetdb.org] On Behalf Of Sharma, Sreejith Sent: Tuesday, August 22, 2017 9:02 AM To: Communication channel for MonetDB users Subject: [EXTERNAL] How to get Memory Dump. Is there any way to eliminate Memory leaks.

All,

Is there any way to get the memory dump from MonetDB?

The memory consumed by merver5 post concurrent query execution are not coming down. Need to investigate why memory leak is happening here.

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