prefork and APR_HAS_THREADS

2007-08-28 Thread Arvind Srinivasan 
Some popular Unix distros package two httpd binaries - one built with the 
prefork MPM and the other built with the worker MPM - but only one set of 
libraries and modules. I assume the libraries and modules are the ones compiled 
for the worker mpm.


Is the performance impact of the APR_HAS_THREADS code blocks in these 
libraries/modules small/neglible as opposed to if they had been built for the 
prefork MPM?


Are there any other implications of using libraries/modules built with 
APR_HAS_THREADS with the prefork MPM?


Thanks,
Arvind

Re: prefork and APR_HAS_THREADS

2007-08-28 Thread William A. Rowe, Jr. 
Arvind Srinivasan wrote:
 Some popular Unix distros package two httpd binaries - one built with
 the prefork MPM and the other built with the worker MPM - but only one
 set of libraries and modules. I assume the libraries and modules are the
 ones compiled for the worker mpm.
 
 Is the performance impact of the APR_HAS_THREADS code blocks in these
 libraries/modules small/neglible as opposed to if they had been built
 for the prefork MPM?

Negligible with a few exceptions.  PHP is one of them, it becomes quite
bulky when you --enable-zts.

Yes, a module built for worker will work against prefork MPM, if the
prefork MPM has been built against a threaded APR.

Bill

Re: prefork and APR_HAS_THREADS

2007-08-28 Thread Plüm , Rüdiger , VF-Group 
IMHO APR_HAS_THREADS has nothing to do with the choice of your MPM (except 
BEOS).
It only tells you if APR has thread support or not and this only
depends on the platform or if you instructed APR explicitly to build
without thread support.

Regards

Rüdiger

 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED] 
 Gesendet: Dienstag, 28. August 2007 12:37
 An: dev@httpd.apache.org
 Betreff: prefork and APR_HAS_THREADS
 
 
 Some popular Unix distros package two httpd binaries - one 
 built with the 
 prefork MPM and the other built with the worker MPM - but 
 only one set of 
 libraries and modules. I assume the libraries and modules are 
 the ones compiled 
 for the worker mpm.
 
 Is the performance impact of the APR_HAS_THREADS code blocks in these 
 libraries/modules small/neglible as opposed to if they had 
 been built for the 
 prefork MPM?
 
 Are there any other implications of using libraries/modules 
 built with 
 APR_HAS_THREADS with the prefork MPM?
 
 Thanks,
 Arvind

Re: prefork and APR_HAS_THREADS

2007-08-28 Thread Arvind Srinivasan 

William A. Rowe, Jr. wrote:


Negligible with a few exceptions.  PHP is one of them, it becomes quite
bulky when you --enable-zts.

Yes, a module built for worker will work against prefork MPM, if the
prefork MPM has been built against a threaded APR.



Thanks.

Arvind

Re: prefork and APR_HAS_THREADS

2007-08-28 Thread Arvind Srinivasan 

Plüm wrote:

IMHO APR_HAS_THREADS has nothing to do with the choice of your MPM (except 
BEOS).
It only tells you if APR has thread support or not and this only
depends on the platform or if you instructed APR explicitly to build
without thread support.


My mistake. I associated APR_HAS_THREADS with the MPM.

Arvind