Re: PostgreSQL as a local in-memory cache
| От | Josh Berkus |
|---|---|
| Тема | Re: PostgreSQL as a local in-memory cache |
| Дата | |
| Msg-id | 4C191F46.4060408@agliodbs.com обсуждение исходный текст |
| Ответ на | Re: PostgreSQL as a local in-memory cache ("jgardner@jonathangardner.net" <jgardner@jonathangardner.net>) |
| Ответы |
Re: PostgreSQL as a local in-memory cache
Re: PostgreSQL as a local in-memory cache |
| Список | 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 по дате отправления: