Re: Running PostgreSQL as fast as possible no matter the consequences

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
Date: 2010-11-05 15:13:34
Message-ID: 8739rfst0h.fsf@cbbrowne.afilias-int.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

gentosaker(at)gmail(dot)com (A B) writes:
> If you just wanted PostgreSQL to go as fast as possible WITHOUT any
> care for your data (you accept 100% dataloss and datacorruption if any
> error should occur), what settings should you use then?

Use /dev/null. It is web scale, and there are good tutorials.

But seriously, there *are* cases where "blind speed" is of use. When
loading data into a fresh database is a good time for this; if things
fall over, it may be pretty acceptable to start "from scratch" with
mkfs/initdb.

I'd:
- turn off fsync
- turn off synchronous commit
- put as much as possible onto Ramdisk/tmpfs/similar as possible
--
output = reverse("moc.liamg" "@" "enworbbc")
http://linuxfinances.info/info/lsf.html
43% of all statistics are worthless.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Devrim GÜNDÜZ 2010-11-05 15:23:35 Re: Running PostgreSQL as fast as possible no matter the consequences
Previous Message Lello, Nick 2010-11-05 12:26:40 Re: Running PostgreSQL as fast as possible no matter the consequences