Re: which is better?

My understanding is that "worker" is faster because it uses threads,
but not all modules that work with Apache are thread safe. There's a
problem with PHP because some third party libraries that PHP might use
are not thread safe. Perl before 5.6 isn't thread safe, etc. Redhat,
by default, comes with prefork because of this.

However, I haven't found any document that states to avoid using
Subversion with "worker" due to threads. If all you're running is
Subversion, you can probably use "worker". But, if you use any other
Apache modules, you have to be careful. For example, if you use ViewVC
or software like this, it could be not thread safe, so you need to
use prefork.

If speed is important, you might want to avoid HTTP altogether and use
svn or svn+ssh.

My experience shows that the server isn't usually the bottleneck with
Subversion. The issues tend to be with the network and client systems.

On Thu, May 6, 2010 at 11:49 PM, west alto <westalto_at_gmail.com> wrote:
> Hi,
>
> Just a question.
>
> I have a server with the following specs:
>
> ESXi guest server
> 2 cpu
> 4 gig memory
>
> Which is better option for running svn and apache, pre-fork or worker?
>
>
> Thanks,
>
>
> West
>

-- 
David Weintraub
qazwart_at_gmail.com