On Wed, Feb 27, 2008 at 4:29 PM, Adriano Manocchia <[EMAIL PROTECTED]> wrote:
> Whoa. No need to get snippy. I was being sincere in my gratitude for
> the suggestions. If nothing else, I'm sure I'll be making more use of
> Xdebug in the future.
I'm not being snippy at all. I was admitting m
Adriano Manocchia wrote:
Whoa. No need to get snippy. I was being sincere in my gratitude for the
suggestions. If nothing else, I'm sure I'll be making more use of Xdebug
in the future.
On Feb 27, 2008, at 3:55 PM, Shawn McKenzie wrote:
Adriano Manocchia wrote:
Well, I just spent more time
Doh, sorry... I was jokingly replying to:
"I was going to suggest that it was most likely an Apache or DNS
issue as opposed to PHP, but after I realized I missed that your "php
tests were run on a single-line PHP script that simply echoed 'hi' so
it couldn't get much simpler than that," I figured
Whoa. No need to get snippy. I was being sincere in my gratitude for
the suggestions. If nothing else, I'm sure I'll be making more use of
Xdebug in the future.
On Feb 27, 2008, at 3:55 PM, Shawn McKenzie wrote:
Adriano Manocchia wrote:
Well, I just spent more time messing with httpd's con
Adriano Manocchia wrote:
> Well, I just spent more time messing with httpd's conf and it the
> problem seems to have resolved itself by turning off hostname lookups. I
> know there's overhead associated with it, but I don't really understand
> why it only affected PHP, and so drastically. At any ra
On Wed, Feb 27, 2008 at 2:50 PM, Adriano Manocchia <[EMAIL PROTECTED]> wrote:
> Well, I just spent more time messing with httpd's conf and it the
> problem seems to have resolved itself by turning off hostname lookups.
> I know there's overhead associated with it, but I don't really
> understand
On Wed, Feb 27, 2008 at 2:34 PM, Adriano Manocchia <[EMAIL PROTECTED]> wrote:
> OK. I just went through about 10 minutes' worth of cachegrinds,
> including several httperf tests on that empty php file (which had the
> usual poor results). According to the cachegrind files, nothing
> (including t
Well, I just spent more time messing with httpd's conf and it the
problem seems to have resolved itself by turning off hostname lookups.
I know there's overhead associated with it, but I don't really
understand why it only affected PHP, and so drastically. At any rate,
I guess this issue is
OK. I just went through about 10 minutes' worth of cachegrinds,
including several httperf tests on that empty php file (which had the
usual poor results). According to the cachegrind files, nothing
(including the other active web pages) took more than 15ms and the
empty php file never excee
I'm trying to get it working but it doesn't seem to want to write the
profile info at the moment. Correct me if I'm wrong, but wouldn't this
just show problems within actual code? If the problem is occurring on
a PHP file with no PHP in it whatsoever, it seems to fall outside the
scope of w
On Wed, Feb 27, 2008 at 12:39 PM, Adriano Manocchia <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've been chasing what I think is the same performance issue for about
> a year and it's driving me batty. First off, the server is a dual core
> 2.8 P4 with 2G RAM running RHEL5 hosted at The Planet and
I know my original post was long-winded, but I did mention that my php
tests were run on a single-line PHP script that simply echoed "hi" so
it couldn't get much simpler than that. But for thoroughness' sake,
I've run the tests against a test file with a php extension with no
PHP code at al
On Wed, Feb 27, 2008 at 12:39 PM, Adriano Manocchia <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've been chasing what I think is the same performance issue for about
> a year and it's driving me batty. First off, the server is a dual core
> 2.8 P4 with 2G RAM running RHEL5 hosted at The Planet and
13 matches
Mail list logo
