Brad Nicholes wrote:
I'm still wondering if we shouldn't just stick with the local 
read/write 
lock on Windows and other single child MPMs (NetWare?) as this should
    
allow better throughput in such cases and yet be safe, right?  In
fact, 
Actually on NetWare this is a non-issue.  On NetWare everything is
global (memory, locks, etc.), so there is no difference between a global
mutex and a local one (other than previously we were using reader/writer
locks rather than mutexes).  I would like to use reader/writer locks
rather than global mutexes simply for performance reasons, but I'm not
sure how we would go about switching between global and local locks
anyway.  This would require #ifdef'ing the code for particular platforms
or MPM's which isn't a good thing.
  
On the contrary, if our #ifdef'ing is localized, I believe that doing this on a per-platform or per-MPM (or better yet a #ifdef HAS_MULTIPLE_WORKER_PROCESSES or some such) basis to maximize performance would be worthwhile.

To scatter such #ifdef's throughout the whole module would be a maintenance nightmare, of course.

--
Jess Holle



Reply via email to