Hello LuaSQL developers,
I'm writing today with two goals in mind:
1. To gain a better understanding of the development/release status of
the project.
2. To offer some financial assistance with development, specifically
assistance to help fix an issue that is affecting anyone trying to use
LuaSQL under high performance scenarios.
So to take those goals one at a time....
Development/release status:
It's not clear to me how LuaSQL is being developed. I can tell a few
things from looking at the github repo and the mailing lists:
1. There is ongoing mailing list discussion, so the project isn't dead.
2. There hasn't been a commit to the source code in almost two months,
so development isn't highly active.
3. There hasn't been an official release in almost two years, so
rolling out new features/bugfixes, is, to say the least, slow... ;)
Do you guys envision this being the pace going forward, or are there
plans to make the project more active?
Financial assistance with development:
Our company has the LuaSQL MySQL driver running on a production
server, which also runs the FreeSWITCH telephony software. FreeSWITCH
comes with Lua embedded, and I'm using LuaSQL to access our database.
Everything worked great in initial testing, but now that we have the
system under some load, a critical problem has emerged: After
somewhere between 1500-2000 queries to the database (this is in a
20-30 minute period), the driver hits this error in the code:
/* Try to init the connection object. */
conn = mysql_init(NULL);
if (conn == NULL)
return luasql_faildirect(L, "error connecting: Out of memory.");
This looks to me like mysql_init() fails because there's not any more
available memory to allocate a new object. at least that's what http://dev.mysql.com/doc/refman/5.0/en/mysql-init.html
seems to suggest.
Once our system starts hitting that error, all queries fail, and the
only way to revive it is to completely restart FreeSWITCH (bad idea on
a live system).
I'm afraid I'm not enough of a Lua/C expert to fix this problem. It's
important to our company that it's fixed, and we have funding
available to pay the LuaSQL developers to fix it. I will add that
this is a time-sensitive issue -- we can't have our production server
crashing randomly throughout the day for very long. If we can't get
the problem fixed rather quickly, we'll probably have to abandon using
LuaSQL altogether.
Please let me know your thoughts on these matters. I look forward to
working with you!
Chad Phillips
Operations Manager
Apartment Lines
http://apartmentlines.com
_______________________________________________
Kepler-Project mailing list
Kepler-Project@lists.luaforge.net
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/
