----- Original Message -----
From: "Zeugswetter Andreas ADI SD" <[EMAIL PROTECTED]>
To: "Takayuki Tsunakawa" <[EMAIL PROTECTED]>; "ITAGAKI
Takahiro" <[EMAIL PROTECTED]>
> > Yes, I used half the size of RAM as the shared buffers, which is
> > reasonable. And I cached all the data.
> For pg, half RAM for shared_buffers is too much. The ratio is good
for
> other db software, that does not use the OS cache.
What percentage of RAM is recommended for shared buffers in general?
40%? 30%? Or, is the general recommendation like "According to the
amount of your data, this much RAM should be left for the kernel
cache. But tha's the story on Linux. It may be different for other
OSes."?
Hmm, if it is so, it sounds hard for system designers/administrators
to judge.
----- Original Message -----
From: "Zeugswetter Andreas ADI SD" <[EMAIL PROTECTED]>
To: "Takayuki Tsunakawa" <[EMAIL PROTECTED]>; "ITAGAKI
Takahiro" <[EMAIL PROTECTED]>
Cc: <pgsql-hackers@postgresql.org>
Sent: Thursday, December 21, 2006 11:04 PM
Subject: RE: [HACKERS] Load distributed checkpoint
> > You were running the test on the very memory-depend machine.
> >> shared_buffers = 4GB / The scaling factor is 50, 800MB of data.
> > Thet would be why the patch did not work. I tested it with DBT-2,
10GB of
> > data and 2GB of memory. Storage is always the main part of
performace here,
> > even not in checkpoints.
>
> Yes, I used half the size of RAM as the shared buffers, which is
> reasonable. And I cached all the data.
For pg, half RAM for shared_buffers is too much. The ratio is good for
other db software, that does not use the OS cache.
Andreas
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
