Hello Nicolas, NC> 'worker' should be better, because it's one process and several threads.
NC> It puts a bit more stress on the GC since there are global locks to NC> obtain when freeing memory, but at the same time, there is more memory NC> available for all the threads, so maybe less GC cycles... But how it will work with threads? I mean - would it be several VMs, or one VM per process with multiple threads? Will they share statics or not? NC> But before doing that, you should maybe : NC> - use neko.Web.cacheModule Done already. NC> - define then environment variable MOD_NEKO_JIT to activate JIT in NC> mod_neko (it's disabled by default) - or always set use_jit to 1. I can define the variable - but how do I set use_jit to 1? In Neko sources? NC> - you can also disable the neko_gc_major() done after each request in NC> mod_neko.c Do you recommend doing that? NC> Right now, mod_neko is focused on getting the best performances without NC> using too much memory, because at MotionTwin we have a lot of Apache NC> processes running, and enough CPU. Well that's what I need as well, I have a memory-constrainted virtual server, so memory is my primary concern. I've also limited the number of processes for prefork MPM to avoid swapping - will probably do more experiments with worker MPM. Maybe it makes sense to create a 'Performance tips' web page on haxe/neko website? -- Best regards, Michael mailto:[EMAIL PROTECTED] -- Neko : One VM to run them all (http://nekovm.org)
