--- On Mon, 3/15/10, Fabio Mascarenhas <[email protected]> wrote:
> I am still not understanding how the memory leak would
> accumulate. Lua
> states are not OS processes, and from what I read in the
> documentation
> you should call mysql_library_init/mysql_library_end on a
> per-OS-process basis (and mysql_library_init is called
> lazily by
> mysql_init the first time you call mysql_init). For the
> MySQL client I
> would assume it makes no difference whether you have
> different Lua
> states or not.
>
My experience said it made a difference. The pattern is like this
Master -> create ring(where the mysql module is loaded and unloaded) then
terminate(properly)
This pattern alone starts memory leak and after a thousand or so ab test, my
host memory has all gone.
Surprisingly
Master(load mysql module and never unload) -> create ring(mysql module load and
unload)
This pattern seems to be ok.
I am not sure if the mentioned fix applies here.
_______________________________________________
Kepler-Project mailing list
[email protected]
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/
