# Question for apache gurus -- error messages during load test

**URL:** <https://www.ruby-forum.com/t/question-for-apache-gurus-error-messages-during-load-test/103580>\
**Category:** Deployment\
**Created:** [May 8, 2007, 3:04am UTC](https://www.ruby-forum.com/t/question-for-apache-gurus-error-messages-during-load-test/103580 "2007-05-08T03:04:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rsanheim](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@rsanheim](https://www.ruby-forum.com/u/rsanheim)\
**Post date:** [May 8, 2007, 3:04am UTC](https://www.ruby-forum.com/t/question-for-apache-gurus-error-messages-during-load-test/103580/1 "2007-05-08T03:04:32Z")

</div>

I’m doing some httperf’ing, and when I’m cranking the load high I see  
things like this in apache:

[Mon May 07 19:45:18 2007] [debug] proxy\_util.c(1724): proxy:  
initialized single connection worker 12 in child 8499 for (_)  
[Mon May 07 19:45:18 2007] [debug] proxy\_util.c(1625): proxy: grabbed  
scoreboard slot 12 in child 8500 for worker proxy:reverse  
[Mon May 07 19:45:18 2007] [debug] proxy\_util.c(1644): proxy: worker  
proxy:reverse already initialized  
[Mon May 07 19:45:18 2007] [debug] proxy\_util.c(1724): proxy:  
initialized single connection worker 12 in child 8500 for (_)  
[Mon May 07 19:45:18 2007] [debug] proxy\_util.c(1625): proxy: grabbed  
scoreboard slot 12 in child 8501 for worker proxy:reverse  
[Mon May 07 19:45:18 2007] [debug] proxy\_util.c(1644): proxy: worker  
proxy:reverse already initialized  
[Mon May 07 19:45:18 2007] [debug] proxy\_util.c(1724): proxy:  
initialized single connection worker 12 in child 8501 for (\*)

I’m guessing thats just noise, and can be safely ignored? googling  
didnt’ turn up anything helpful.

Also, this:

[Mon May 07 19:45:19 2007] [info] server seems busy, (you may need to  
increase StartServers, or Min/MaxSpareServers), spawning 8 children,  
there are 0 idle, and 209 total children

This last one always happens with many children spawned, when I start  
using a rate of \>70 or something like that. So requests were piling  
up in apache, which is expected, but should I really adjust the  
prefork settings for this? This is what i have right now:

StartServers 10  
MinSpareServers 8  
MaxSpareServers 30  
ServerLimit 256  
MaxClients 256  
MaxRequestsPerChild 4000

This is apache 2.3, mongrel latest, ruby 185/rails123 stable, hitting  
a pretty complex page that is using a lot of fragment caching in  
memcached. No DB hits, though, as everything should be sitting in  
memcached. The machine is a quad core intel with 4 gig ram, iirc.

thx,

- Rob  
–  
[http://robsanheim.com](http://robsanheim.com)  
[http://seekingalpha.com](http://seekingalpha.com)