Obi a écrit :
Hi all, I've been playing around with mod_tora neko application server compiled from 1.8.1 sources. It is working just fine except that I wonder why and how exactly the server loads new module instance where it had been initially started with "Web.cacheModule(Main.handleRequests);"
If there are several simultaneous requests, Tora will allocate additional instance. That means that you can have up to N instance in memory, where N is your number of threads.
What is problematic for me is that when I fire up 200 asynch requests upon that cached module, the tora server just hangs for awhile, which blocks any other requests to other modules within the tora server to be executed.
Yes, that's normal, there is currently no way to maximimize the number of threads used for given service. You'll have to run one tora server per-service (on same machine, different ports) and configure Apache so it connect on the good server/port depending on the service.
And if yes - how is possible to wire up persistent/cached neko application within mod_tora? By having one tora server per every application? Or by forking new version of tora capable to handle large amount of requests at the same time?
You can host persistent data among several instance with the new api tora.Share, see http://ncannasse.fr/blog/tora_comet
Best, Nicolas -- Neko : One VM to run them all (http://nekovm.org)
