| From: | Greg Copeland <greg(at)CopelandConsulting(dot)Net> |
|---|---|
| To: | "Samuel J(dot) Sutjiono" <ssutjiono(at)wc-group(dot)com> |
| Cc: | PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RAMDISK |
| Date: | 2002-07-23 14:56:44 |
| Message-ID: | 1027436205.6415.111.camel@mouse.copelandconsulting.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Interesting results. You didn't really offer much in how your system
was configured to use the ramdisk. Did you use it to simply store a
database on it? Was the entire database able to fit into available
memory even without the RAMDISK? Did you try only storing indicies on
the RAMDISK? There are lots of other questions that unanswered on the
topic.
Worth mentioning that it is very possible and in fact, fairly easy to
do, for the use of a RAMDISK to significantly hinder the performance of
a system running a database.
Greg
On Tue, 2002-07-23 at 09:36, Samuel J. Sutjiono wrote:
> I've finally got around to try RAMDISK with PostgreSQL. The attached doc
> contains the test results that I'd like to share with PostgreSQL's users
> and developers groups.
>
> Regards,
> Samuel Sutjiono
> _________________________________________________
> Expand your wireless world with Arkdom PLUS
> http://www.arkdom.com/
>
> ----
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-07-23 15:34:39 | Re: [PATCHES] prepareable statements |
| Previous Message | Samuel J. Sutjiono | 2002-07-23 14:36:13 | RAMDISK |