John Peacock <jpeacock@rowman.com> writes:
> He is running on dangerously low physical RAM machines. Windows (as a
> rule) does not gracefully handle low memory situations. The swap on
> Windows is not employed in quite the same fashion as the swap on *nix
> boxen (meaning that frequently more swap is slower than less).
> Between the Berkeley DLL's and Apache itself, I suspect he has
> virtually no free RAM available. If he configured Apache to start
> fewer child processes, he might be in better shape.
>
> I think he is simply swapping himself to death and triggering edge
> conditions in Berkeley because of it.
When I fire up my httpd on Linux, I get about 8 mpm-prefork children,
each about 3 megs in size. After even the most gigantic svn
operations, the largest child never grows bigger than 10 megs.
How could this be a problem with swap? He's saying that child httpd
processes are growing up to 80 megs and beyond. Are you suggesting
that if his machine had a gig of RAM, that his httpd processes
*wouldn't* grow to 80 megs and beyond?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 23 17:08:35 2003