To be more clear, I cannot figure out the reason why mserver acts like that. Query doesn't seem very complicated to me. Should i refine my query or is it a problem of mserver (e.g. configuration issue, bug etc)? On Thu, May 12, 2011 at 4:09 PM, George Garbis <ggarbis@di.uoa.gr> wrote:
This is right (confirmed by dmesg), but why does mserver overuse memory for a query like that?
On Thu, May 12, 2011 at 3:44 PM, Fabian Groffen <Fabian.Groffen@cwi.nl>wrote:
On 12-05-2011 15:37:30 +0300, Georgios Garmpis wrote:
Hi,
Please find attached a query (and corresponding schema) that results in mserver5 using more than 1GB of memory and terminating after 6 mins with this output:
2011-05-12 15:28:14 MSG merovingian[4114]: database 'testQuery' (4121) was killed by signal SIGKILL
I think your OS' OOM killer killed your database here. Can you check your dmesg output?
------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- George Garbis
-- George Garbis