Re: RESOLVED: Re: Wierd context-switching issue on Xeon - Mailing list pgsql-performance

From Josh Berkus
Subject Re: RESOLVED: Re: Wierd context-switching issue on Xeon
Date
Msg-id 200404160958.14902.josh@agliodbs.com
Whole thread Raw
In response to RESOLVED: Re: Wierd context-switching issue on Xeon  (Dirk Lutzebäck <lutzeb@aeccom.com>)
Responses Re: RESOLVED: Re: Wierd context-switching issue on Xeon  (Dirk Lutzebäck <lutzeb@aeccom.com>)
List pgsql-performance
Dirk,

> I'm not sure if this semop() problem is still an issue but the database
> behaves a bit out of bounds in this situation, i.e. consuming system
> resources with semop() calls 95% while tables are locked very often and
> longer.

It would be helpful to us if you could test this with the indexes disabled on
the non-Bigmem system.   I'd like to eliminate Bigmem as a factor, if
possible.

--
-Josh Berkus

______AGLIO DATABASE SOLUTIONS___________________________
                                        Josh Berkus
    Enterprise vertical business        josh@agliodbs.com
     and data analysis solutions        (415) 752-2387
      and database optimization           fax 651-9224
  utilizing Open Source technology      San Francisco


pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Horribly slow hash join
Next
From: Josh Berkus
Date:
Subject: Re: Index Problem?