> Yes, I have been mulling over this all weekend. > Is there a greater demand for a Unicorn/php-fpm style fastcgi process > manager? If you set luafcgid to 1 worker thread and (let's say) 5 states, > then run a couple of them - you have basically a redundant, multiplexed, > single-threaded Lua FastCGI server.
> I tested it and it runs fine, just uses significantly more memory: > > 1 luafcgid process w/10 threads and 50 states: > 5828K total, 1384K resident > 10 luafcgid processes w/1 thread and 5 states each: > 46760K total, 12600K resident > On a 256MB slicehost (for example), that is starting to get painful. I'm, personally, more interested in dedicated server hardware case. So the RAM is not THAT big issue for me. <...> > With 10 worker threads and nginx, "ab -c 10 -n 10 > http://x.x.x.x/multiplex-test.lua"; gives almost 10 rps, each one taking just > over 1 sec. If any take 2 secs or more, then the webserver is serializing > requests. Sorry for the stupid question, but you are of course, aware, that ab -c 10 still runs in a single thread? (I'm asking because I've figured this out only recently.) > I could perhaps shift gears and make a Lua-fpm. This would be a parent > process that fires off off multiple child processes - each one being a > FastCGI server & Lua state manager with housekeeping (luafcgid with only one > worker thread). > Thoughts? So far, I'm not sold neither for luafcgid, nor for Lua-fpm. But that's only because I'm still thinking to write one of them myself (or even both). :-) Alexander. _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
