I have seen this before. I belive it is realated to the hash table allocation,
which are very large (actually larger than they need to be due to estimation
errors). Tcmalloc warns on such allocations.
BTW: Jianqiao and Harshad, can we reduce the initial hash table allocation. I
think starting with something small e.g, 8K entries and then doubling as needed
(the code already does that) should work. We can try it.
Cheers,
Jignesh
On 9/2/16, 9:48 PM, "Navneet Potti" <po...@wisc.edu> wrote:
As an aside, I also get this warning often when running some of the later
queries.
tcmalloc: large alloc 1610612736 bytes == 0x99ed4000 @
tcmalloc: large alloc 1610612736 bytes == 0x89ec4000 @
tcmalloc: large alloc 1610612736 bytes == 0x89ec4000 @
