> Hello list, > > I am now trying to speed up my apache+mod_neko web server, and I > have a question - how does mod_neko work with different Apache MPMs? > For instance, will it work if I replace default 'prefork' MPM with > 'worker' one? And if anybody knows whether I can speed up this way, > this would be also helpful.
'worker' should be better, because it's one process and several threads. It puts a bit more stress on the GC since there are global locks to obtain when freeing memory, but at the same time, there is more memory available for all the threads, so maybe less GC cycles... But before doing that, you should maybe : - use neko.Web.cacheModule - define then environment variable MOD_NEKO_JIT to activate JIT in mod_neko (it's disabled by default) - or always set use_jit to 1. - you can also disable the neko_gc_major() done after each request in mod_neko.c Right now, mod_neko is focused on getting the best performances without using too much memory, because at MotionTwin we have a lot of Apache processes running, and enough CPU. Nicolas -- Neko : One VM to run them all (http://nekovm.org)
