| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | Vitalii Tymchyshyn <tivv00(at)gmail(dot)com> |
| Cc: | Niels Kristian Schjødt <nielskristian(at)autouncle(dot)com>, Kevin Grittner <kgrittn(at)mail(dot)com>, <pgsql-performance(at)postgresql(dot)org>, Willem Leenen <willem_leenen(at)hotmail(dot)com> |
| Subject: | Re: Optimize update query |
| Date: | 2012-11-30 14:06:48 |
| Message-ID: | 50B8BD78.9050805@optionshouse.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 11/30/2012 02:37 AM, Vitalii Tymchyshyn wrote:
> Actually, what's the point in putting logs to ssd? SSDs are good for
> random access and logs are accessed sequentially.
While this is true, Niels' problem is that his regular HDs are getting
saturated. In that case, moving any activity off of them is an improvement.
Why not move the data to the SSDs, you ask? Because he bought two 3TB
drives. The assumption here is that a 256GB SSD will not have enough
space for the long-term lifespan of this database.
Either way, based on the iostat activity he posted, clearly there's some
other write stream happening we're not privy to.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bob Jolliffe | 2012-11-30 14:34:15 | deadlock under load |
| Previous Message | Shaun Thomas | 2012-11-30 14:02:39 | Re: Optimize update query |