Re: PostgreSQL as a local in-memory cache - Mailing list pgsql-performance

From Josh Berkus
Subject Re: PostgreSQL as a local in-memory cache
Date
Msg-id 4C191F46.4060408@agliodbs.com
Whole thread Raw
In response to Re: PostgreSQL as a local in-memory cache  ("jgardner@jonathangardner.net" <jgardner@jonathangardner.net>)
Responses Re: PostgreSQL as a local in-memory cache  (Jonathan Gardner <jgardner@jonathangardner.net>)
Re: PostgreSQL as a local in-memory cache  (Craig James <craig_james@emolecules.com>)
List pgsql-performance
> * fsync=off => 5,100
> * fsync=off and synchronous_commit=off => 5,500

Now, this *is* interesting ... why should synch_commit make a difference
if fsync is off?

Anyone have any ideas?

> tmpfs, WAL on same tmpfs:
> * Default config: 5,200
> * full_page_writes=off => 5,200
> * fsync=off => 5,250
> * synchronous_commit=off => 5,200
> * fsync=off and synchronous_commit=off => 5,450
> * fsync=off and full_page_writes=off => 5,250
> * fsync=off, synchronous_commit=off and full_page_writes=off => 5,500

So, in this test, it seems like having WAL on tmpfs doesn't make a
significant difference for everything == off.

I'll try running some tests on Amazon when I have a chance.  It would be
worthwhile to get figures without Python's "ceiling".

--
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com

pgsql-performance by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: PostgreSQL as a local in-memory cache
Next
From: Juan Pablo Sandoval Rivera
Date:
Subject: Confirm calculus