Optimising apache on a single core 32bit machine with hyperthreading
On Saturday 24 Sep 2011 11:12:48 Florian Philipp wrote:
> Am 24.09.2011 11:32, schrieb Mick:
> > If I haven't enabled USE= apache2_mpms_prefork and apache2_mpms_worker,
> > how does apache behave with regards to threading responses?
> If you have neither enabled, the ebuild (apache-2 eclass, to be
> specific) chooses one of them based on USE=threads. Enabled=worker,
I have threads unset globally so from what you're saying apache must be
running in preforked mode. I thought that I would need to define explicitely
USE="apache2_mpms_prefork" and enable or configure this in the apache modules
(I couldn't find any configurations related to preforked when I looked).
I'm trying to troubleshoot why a dev't machine that also runs a KDE desktop
continues to freeze after a few hours of heavy usage (and repeated reloading
of web pages for testing). It usually unlocks itself if left alone over a
coffee break - say after 5 -15 minutes depending on how many desktop apps are
running at the time.
I don't think it is apache that causes it (I'm suspecting KDE of course ;p ),
but it may be one of the things that contributes to it.