From: Mark Felder <feld@feld.me>
To: pgsql-performance@postgresql.org
Subject: Re: Migrating to Postgresql and new hardware
Date: Tue, 18 Jan 2011 16:53:29 -0600
Message-ID: <op.vpi0jfzv34t2sn@tech304> (raw)
In-Reply-To: <EF37296944B47C40ADDCCB7BFD6289FE046FCD5EFC@EMASC201VS01.exchad.jpmchase.net>
References: <E0B1224AD40B544B9DE1BCC6008E95220D1F192CC2@UF05.unifaun.se>
<EF37296944B47C40ADDCCB7BFD6289FE046FCD5EFC@EMASC201VS01.exchad.jpmchase.net>
On Tue, 18 Jan 2011 16:06:17 -0600, Strange, John W
<john.w.strange@jpmchase.com> wrote:
> Of course this is based on my experience, and I have my fireproof suit
> since I mentioned the word fusionIO :)
I'll throw a fire blanket up as well. We have a customer who has been
running Fusion IO with Postgres for about 2 years. They get amazing
performance, but also aren't running fsync. They haven't had corruption
with OS crashes (they're very abusive to their CentOS install), but did
with a power outage (a UPS of ours went up in smoke; they weren't paying
for N+1 power). Now their data is mostly static; they run analytics once a
day and if they have a problem they can reload yesterday's data and run
the analytics again to get back up to speed. If this is the type of stuff
you're doing and you can easily get your data back to a sane state by all
means give FusionIO a whirl!
This customer did discuss this with me in length last time they stopped in
and also pointed out that FusionIO was announced as being a major part of
some trading company or bank firm's database performance junk. I don't
know the details, but I think he said they were out of Chicago. If anyone
knows what I'm talking about please share the link. Either way, it seems
that people are actually doing money transactions on FusionIO, so you can
either take that as comforting reassurance or you can start getting really
nervous about the stock market :-)
Regards,
Mark
PS, don't turn off fsync unless you know what you're doing.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: feld@feld.me
Subject: Re: Migrating to Postgresql and new hardware
In-Reply-To: <op.vpi0jfzv34t2sn@tech304>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox