Re: [PATCHES] O_DIRECT for WAL writes

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [PATCHES] O_DIRECT for WAL writes
Дата
Msg-id 26018.1119620243@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [PATCHES] O_DIRECT for WAL writes  (ITAGAKI Takahiro <itagaki.takahiro@lab.ntt.co.jp>)
Ответы Re: [PATCHES] O_DIRECT for WAL writes  ("Jim C. Nasby" <decibel@decibel.org>)
Re: [PATCHES] O_DIRECT for WAL writes  (ITAGAKI Takahiro <itagaki.takahiro@lab.ntt.co.jp>)
Re: [PATCHES] O_DIRECT for WAL writes  ("Jeffrey W. Baker" <jwb@gghcwest.com>)
Список pgsql-hackers
ITAGAKI Takahiro <itagaki.takahiro@lab.ntt.co.jp> writes:
> ... So I'll post the new results:

> checkpoint_ | writeback | 
> segments    | cache     | open_sync | fsync=false   | O_DIRECT only | fsync_direct  | open_direct
> ------------+-----------+-----------+---------------+---------------+---------------+--------------
> [3]   3     | off       |  38.2 tps | 138.8(+263.5%)|  38.6(+ 1.2%) |  38.5(+ 0.9%) |  38.5(+ 0.9%)

Yeah, this is about what I was afraid of: if you're actually fsyncing
then you get at best one commit per disk revolution, and the negotiation
with the OS is down in the noise.

At this point I'm inclined to reject the patch on the grounds that it
adds complexity and portability issues, without actually buying any
useful performance improvement.  The write-cache-on numbers are not
going to be interesting to any serious user :-(
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: William White
Дата:
Сообщение: Re: Fixing r-tree semantics
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: [PATCHES] Function's LEAST, GREATEST and DECODE (Oracle