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);"
Here is what I'm missing: I ran one simple console application under neko creating 200 Threads, every thread having only one "haxe.Http.requestUrl " call to the cached module. What I see in tora_admin.n is that the module get loaded several times even in the case that it is shown as one instance. So I assume that the module had been loaded several times by the worker threads of the mod_tora server, which in that case allocates the module in new memory segment ? 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. Is the above block related to this as stated in http://ncannasse.fr/blog/mod_tora : "Several instance of the same module can be put into memory if needed, depending on the number of threads that will need to simultaneously execute a given module." 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? Kind regards, Boris PS. I've tested the above scenario using linux's 'ab' utility which also proved that tora or the module itself hangs. Also per every request to the module -> it creates one mySQL query, which may also lead to that block (?) -- Neko : One VM to run them all (http://nekovm.org)
