The first step would be to try to quantify the performance
difference in serving the actual web pages. Find a single
page that you think is slow on the production system and that
can be accessed without having to be part of a session, and
quantify the performance difference for that page.
I'm pretty confused right now with trying to determine the
nature of a
performance problem I'm having on one of my servers. The
server is a
webserver with a separate db/file server sitting behind it.
The issue
is that in pulling up websites from the machine, my silly POS
On Thu, 11 Sep 2003, John Straiton wrote:
Greets!
I'm pretty confused right now with trying to determine the nature of a
performance problem I'm having on one of my servers. The server is a
webserver with a separate db/file server sitting behind it. The issue is
that in pulling up websites
John Straiton writes:
I'm pretty confused right now with trying to
determine the nature of a performance problem ...
on one of my servers. ... in pulling up websites
from the machine, my silly POS development
box has nearly double performance ...
There's lots of tricky stuff that can be
Post your kernel configs, or better yet, do a diff -u between
the 5.0-R and the 5.1-C kernel configs. I bet dime to dollar
you've got some debugging options enabled in the 5.1-C
config. At the very least you haven't remove the debugging
options from your malloc options.
*frown* The 5.0
There's lots of tricky stuff that can be going wrong.
I spent some time in my last two jobs (anybody got
a new one in NJ?) on speeding up stuff like this
and the first thing I try to do is put some kind of
steady-state load on the boxen and monitor each box involved
with systat 1 -vmstat
Post your kernel configs, or better yet, do a diff -u between the
5.0-R and the 5.1-C kernel configs. I bet dime to dollar you've
got some debugging options enabled in the 5.1-C config. At the
very least you haven't remove the debugging options from your
malloc options.
*frown* The
On Thu, Sep 11, 2003 at 05:30:59PM -0400, John Straiton wrote:
If 5.1-C has debugging on by default then , yes, I'd concur that we have
those features turned on.
5.1-CURRENT indeed has a number of debugging features enabled by
default, which can cause significant performance loss under load.
