| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Dmytrii Nagirniak <dnagir(at)gmail(dot)com> |
| Cc: | Jan Kesten <jan(at)dafuer(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Optimise PostgreSQL for fast testing |
| Date: | 2012-02-23 06:05:56 |
| Message-ID: | CAFj8pRD8xUoKxhxctj41gTtFzAb7ZakcBVFOF-nxPu4ewSQ7iQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello
SQLite should be faster in single user test - it is optimized for this
purpose. So you cannot to get same speed from PostgreSQL
Pavel
2012/2/23 Dmytrii Nagirniak <dnagir(at)gmail(dot)com>:
>
>
> On 23/02/2012, at 4:38 PM, Jan Kesten wrote:
>
> Hi Dmytrii,
>
> just as short idea, put "fsync = off" in your postgres.conf. That turns off
> that after a commit data is forcilby written to disk - if the database
> crashes there might be dataloss.
>
>
> Thanks. So far I tried:
>
> fsync = off
> full_page_writes = off
>
> It seems it got a *little* faster (down to ~65 seconds from ~76) but is till
> too far from my target of ~34 secs.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stuart Bishop | 2012-02-23 06:21:40 | Re: Measuring replication lag time |
| Previous Message | Dmytrii Nagirniak | 2012-02-23 06:02:38 | Re: Optimise PostgreSQL for fast testing |