Hi,
at first, many thanks for your valuable replies. On my quest for the
ultimate hardware platform I'll try to summarize the things I learned.
-
This is our current setup:
Hardware:
Dual Xeon DP 2.4 on a TYAN S2722-533 with HT enabled
3
On May 12, 2004, at 3:22 PM, [EMAIL PROTECTED] wrote:
I don't see that. But I also set checkpoint segments to about 50 on
my big server.
But wouldn't that affect checkpoint frequency, not checkpoint cost
Seems reasonable. I suppose checkpointing doesn't cost as much disk
I/O as vacuum does. My
Quoting Vivek Khera <[EMAIL PROTECTED]>:
> > "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
>
> TL> Jack Orenstein <[EMAIL PROTECTED]> writes:
> >> I'm looking at one case in which two successive transactions, each
> >> updating a handful of records, take 26 and 18 *seconds* (not msec) to
> >>
> "JAR" == J Andrew Rogers <[EMAIL PROTECTED]> writes:
JAR> The LSI MegaRAID reading/writing/caching behavior is user configurable.
JAR> It will support both write-back and write-through, and IIRC, three
JAR> different algorithms for reading (none, read-ahead, adaptive). Plenty
JAR> of confi
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> Jack Orenstein <[EMAIL PROTECTED]> writes:
>> I'm looking at one case in which two successive transactions, each
>> updating a handful of records, take 26 and 18 *seconds* (not msec) to
>> complete. These transactions normally complete in unde
Doug Y wrote:
Hello,
I've been having some performance issues with a DB I use. I'm trying
to come up with some performance recommendations to send to the
"adminstrator".
Hardware:
CPU0: Pentium III (Coppermine) 1000MHz (256k cache)
CPU1: Pentium III (Coppermine) 1000MHz (256k cache)
Memory: 3
On Wed, 12 May 2004, Grega Bremec wrote:
> ...and on Tue, May 11, 2004 at 03:02:24PM -0600, scott.marlowe used the keyboard:
> >
> > If you get the LSI megaraid, make sure you're running the latest megaraid
> > 2 driver, not the older, slower 1.18 series. If you are running linux,
> > look for
On Tue, 11 May 2004 15:46:25 -0700, Paul Tuckfield <[EMAIL PROTECTED]>
wrote:
>- the "cache" column shows that linux is using 2.3G for cache. (way too
>much)
There is no such thing as "way too much cache".
> you generally want to give memory to postgres to keep it "close" to
>the user,
Yes,
Sorry .. I am a newbie and I don't know :(
How can I know that I am in C locale ?
How can I change my database to use C locale?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Kings-Lynne
Sent: Wednesday, May 12, 2004 3:59 PM
To: Michael Rya
Are you in a non-C locale?
Chris
Michael Ryan S. Puncia wrote:
Yes , I already do that but the same result .. LIKE uses seq scan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Kings-Lynne
Sent: Wednesday, May 12, 2004 2:48 PM
To: Michael Ry
Yes , I already do that but the same result .. LIKE uses seq scan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Kings-Lynne
Sent: Wednesday, May 12, 2004 2:48 PM
To: Michael Ryan S. Puncia
Cc: [EMAIL PROTECTED]
Subject: Re: [PERFORM] Using LI
11 matches
Mail list logo