From: J. Andrew Rogers <jrogers@neopolitan.com>
To: pgsql-performance@postgresql.org
Subject: Re: Wierd context-switching issue on Xeon
Date: 19 Apr 2004 10:55:50 -0700
Message-ID: <1082397350.30934.34.camel@localhost.localdomain> (raw)
In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509813F@vt-pe2550-001.vantage.vantage.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509813F@vt-pe2550-001.vantage.vantage.com>
I decided to check the context-switching behavior here for baseline
since we have a rather diverse set of postgres server hardware, though
nothing using Xeon MP that is also running a postgres instance, and
everything looks normal under load. Some platforms are better than
others, but nothing is outside of what I would consider normal bounds.
Our biggest database servers are Opteron SMP systems, and these servers
are particularly well-behaved under load with Postgres 7.4.2. If there
is a problem with the locking code and context-switching, it sure isn't
manifesting on our Opteron SMP systems. Under rare confluences of
process interaction, we occasionally see short spikes in the 2-3,000
cs/sec range. It typically peaks at a couple hundred cs/sec under load.
Obviously this is going to be a function of our load profile a certain
extent.
The Opterons have proven to be very good database hardware in general
for us.
j. andrew rogers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jrogers@neopolitan.com
Subject: Re: Wierd context-switching issue on Xeon
In-Reply-To: <1082397350.30934.34.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox