From: | "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de> |
---|---|
To: | "Allan Kamau" <kamauallan(at)gmail(dot)com>, "Postgres General Postgres General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Considering Solid State Drives |
Date: | 2010-11-11 08:55:05 |
Message-ID: | C4DAC901169B624F933534A26ED7DF31034BB8CC@JENMAIL01.ad.intershop.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
SSD caveats are well described here:
http://www.postgresql.org/about/news.1249
HTH,
Marc Mamin
-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Allan Kamau
Sent: Donnerstag, 11. November 2010 07:42
To: Postgres General Postgres General
Subject: [GENERAL] Considering Solid State Drives
Hi,
As part of datamining activity. I have some plpgsql functions
(executed in parallel, up to 6 such concurrent calls) that perform
some reads and writes of large number of (maybe 10000) records at a
time to a table having multi-column primary key.
It seems the writing of these few thousands records is taking a long
time (up to 5mins in some cases).
Running vmstat reports %iowait between 15 and 24 on a single 7200rpm
SATA drive, six core (Phenom II) "server".
I am now thinking of investing in a SSD (Solid State Drive), and maybe
choosing between "Crucial Technology 256GB Crucial M225 Series
2.5-Inch Solid State Drive (CT256M225)" and "Intel X25-M G2 (160GB) -
Intel MLC". I have looked at the comparison statistics given here
"http://www.anandtech.com/bench/Product/137?vs=126" that suggests that
the Intel offering is more geared for small random write operations.
After googling I found little resent content (including survival
statistics) of using SSDs in a write intensive database environment.
Kindly advice,
Allan.
From | Date | Subject | |
---|---|---|---|
Next Message | Radosław Smogura | 2010-11-11 11:21:31 | Re: Considering Solid State Drives |
Previous Message | Marc Mamin | 2010-11-11 08:48:38 | Re: dblink_get_result issue |