[KinoSearch] memory use

[Peter Karman]

Marvin Humphrey wrote on 1/24/10 12:49 PM:

> As of r5749, test_valgrind is fixed and passes.  I found a few small memory
> leaks here and there, but nothing that would cause a jump from 80 MB to 600
> MB.  Does this problem also persist after a "./Build realclean"?

yes.

however, I realize I wasn't comparing apples with apples. I ran 0.30072 with 
fewer sortable fields, since it doesn't support sortable FullTextType, and I ran 
svn trunk with all FullTextType fields sortable. So the memory use could be due 
to that.

I will rerun more comparable config and report back.


-- 
Peter Karman  .  http://peknet.com/  .  peter at peknet.com