From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | Chris Hoover <revoohc(at)gmail(dot)com> |
Cc: | PGSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Benchmarking a large server |
Date: | 2011-05-10 07:24:18 |
Message-ID: | BANLkTimsRfJ-q8vWtGq-WD2ciAxuE3UWKQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, May 9, 2011 at 10:32 PM, Chris Hoover <revoohc(at)gmail(dot)com> wrote:
> So, does anyone have any suggestions/experiences in benchmarking storage
> when the storage is smaller then 2x memory?
Try writing a small python script (or C program) to mmap a large chunk
of memory, with MAP_LOCKED, this will keep it in RAM and avoid that
RAM from being used for caching.
The script should touch the memory at least once to avoid overcommit
from getting smart on you.
I think only root can lock memory, so that small program would have to
run as root.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hägi | 2011-05-10 09:20:34 | Re: indexes ignored when querying the master table |
Previous Message | Sethu Prasad | 2011-05-10 07:23:13 | Re: Postgres 9.0.4 + Hot Standby + FusionIO Drive + Performance => Query failed ERROR: catalog is missing 1 attribute(s) for relid 172226 |