MELLOC -erros

Moderator: NorbertKrupa

jpcavanaugh
Intermediate
Intermediate
Posts: 149
Joined: Mon Apr 30, 2012 10:04 pm
Location: New York
Contact:

Re: MELLOC -erros

Post by jpcavanaugh » Tue Sep 18, 2012 10:02 pm

Can you enable join spill and try rerunning the query?

adrian.oprea
Intermediate
Intermediate
Posts: 163
Joined: Tue Jun 19, 2012 2:44 pm
Location: Rio de Janeiro
Contact:

Re: MELLOC -erros

Post by adrian.oprea » Tue Sep 18, 2012 10:29 pm

Ok i have added more datafile as temp space , but cannot find any parameter that holds the spill value!!!
How to do this !!
trying so hard !!!

jpcavanaugh
Intermediate
Intermediate
Posts: 149
Joined: Mon Apr 30, 2012 10:04 pm
Location: New York
Contact:

Re: MELLOC -erros

Post by jpcavanaugh » Wed Sep 19, 2012 1:50 am

This is just a test without seeing anything going on with your system so please only try this for testing purposes only (non-production).

select set_vertica_options('EE','ENABLE_JOIN_SPILL');

adrian.oprea
Intermediate
Intermediate
Posts: 163
Joined: Tue Jun 19, 2012 2:44 pm
Location: Rio de Janeiro
Contact:

Re: MELLOC -erros

Post by adrian.oprea » Wed Sep 19, 2012 12:44 pm

HY,
I don't know if this did the trick , because the query takes again a lot of time and my host memory is down to 15 mb, maybe because of the 95% ratio that the general pool is allowed to take!!
Now from i have read and i can understand Vertica when doing join (hash/merge/etc..) on 2 or more tables it stores them in memory , and if data wont fit it will "spill " the data on to disk-but performance is poor!!!!
And what this lead us to think is that Vertica is memory addict when tables are big (which they always are !! this is the work of Vertica).
Why this conclusion:
-after 2 days of "zero" improvement i decided to create a new ENV with the same data but different arch :
ENV 1 (2 node with 2 cpu each and 2 Gb memory) -- query time 770 sec
ENV 2 (single node 8 cpu and 8 Gb memeory)-- query time 420 sec
-where is the cluster help ? so is just the memory increase that will make Vertica run faster :( !! not good , or this is not what i have read in all those cases !! hhmm imagine Zinga with 20 TB table running it's DB on a let's say 6 GB mem on x nodes , impossible in this ENV.

I have a 3 tables :

Code: Select all

dbadmin=> select count(*) from ANT;
 count
-------
  6341
(1 row)
dbadmin=> select count(*) from BIL;
   count
-----------
 279313436
(1 row)
dbadmin=> select count(*) from SUB;
  count
----------
 19986818
(1 row)
And i will attach my explain plan as well !!!
trying so hard !!!

adrian.oprea
Intermediate
Intermediate
Posts: 163
Joined: Tue Jun 19, 2012 2:44 pm
Location: Rio de Janeiro
Contact:

Re: MELLOC -erros

Post by adrian.oprea » Wed Sep 19, 2012 12:58 pm

Where can i find this options that i have posted here because in the documentation they are not ?
trying so hard !!!

jpcavanaugh
Intermediate
Intermediate
Posts: 149
Joined: Mon Apr 30, 2012 10:04 pm
Location: New York
Contact:

Re: MELLOC -erros

Post by jpcavanaugh » Wed Sep 19, 2012 2:55 pm

I would suggest setting up a time to talk with your SE because this should work good without issues. BTW, the minimum is 2G of ram per core.

adrian.oprea
Intermediate
Intermediate
Posts: 163
Joined: Tue Jun 19, 2012 2:44 pm
Location: Rio de Janeiro
Contact:

Re: MELLOC -erros

Post by adrian.oprea » Wed Sep 19, 2012 4:05 pm

We are already doing so.
Thank you Joe for the help, but please give an opinion on my last post on this thread !since i want to understand better the way Vertica works !!
And i want to add that the documentation need to improve !
THX
i appreciate your effort
trying so hard !!!

Post Reply

Return to “Vertica Database Administration”