Posted by "Nicolas Ross" on 09/14/05 18:10

Hostname lookup is always off in all config. There is no allow, deny
directive with hostnames.

In my original post, I said I've tested with apache 1.3 and 2.0.

And btw, I forgot to mention an important point, during the 8-15 seconds it
takes to display the page, the particular thread serving this page eats
close to 100% of 1 cpu.

Nicolas

----- Original Message -----
From: "Brent Baisley" <brent@landover.com>
To: "Nicolas Ross" <rossnick-lists@cybercat.ca>
Cc: <php-general@lists.php.net>
Sent: Wednesday, September 14, 2005 10:46 AM
Subject: Re: [PHP] php Slow with Mac OS X 10.4


> There are two thing to check in the Apache config to make sure DNS is not
> the thing slowing you down.
> HostnameLookups defaults to On in Apache2, but defaulted to off in
> Apache1. Check that setting.
>
> Also, if you use Allow and Deny directives with domain names, Apache does
> a double reverse triple lindy DNS lookup (or something like that). That
> would slow things down alot, but not affect ssh, ftp, etc.
>
> Regardless, my guess is it's something with Apache2 that is causing the
> slow down. Have you tried Apache1.3 under 10.4? I haven't experienced any
> performance slow down under 10.4 using 1.3.
>
>
> On Sep 14, 2005, at 9:57 AM, Nicolas Ross wrote:
>
>>>> In all cases, it was the same httpd.conf. Of course, from apache 1 to
>>>> 2 there where differences, but basicly it's the same.
>>>>
>>>
>>> your description gives the impression that there is a DNS configuration
>>> problem...
>>> like apache is trying for 5-10 seconds to look something up, fails and
>>> then finally
>>> decides to run your script.
>>>
>>> you can test that with a simple script like:
>>>
>>> <?php /*make sure all outputbuffering is off!*/ for ($i=0;$i <
>>> 100000;$i++) { echo "$i<br />"; } ?>
>>>
>>> chances are it will start outputting after a certain ammount of time
>>> rather than right away.
>>> that said this is a very simplistic test and my understanding of this
>>> stuff is rather limited.
>>>
>>
>> It did occure to me that there maybe a dns issue, but it can't be. My
>> tests were done on two separates server rooms. In the second one (the
>> one with the xserves), I have 3 computers. All ip config is exactly the
>> same (apart from main ip)... And the only non-network related difference
>> between the nodes are the OS (10.3 vs 10.4).
>>
>> Besides, if it were a DNS problem, I would also experience delays
>> elswhere, like ssh, ftp an other things network-related.
>>
>> I did the test, and it started to output immediatly...
>>
>> Thanks,
>>
>> Nicolas

[Back to original message]