Re: Use pread and pwrite instead of lseek + write and read
От | Robert Haas |
---|---|
Тема | Re: Use pread and pwrite instead of lseek + write and read |
Дата | |
Msg-id | CA+TgmobEq_C2t=bqBCQnwwgfXDMbbVdfndpkfyY4vCtZFveQ2A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Use pread and pwrite instead of lseek + write and read (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Use pread and pwrite instead of lseek + write and read
|
Список | pgsql-hackers |
On Wed, Aug 17, 2016 at 9:40 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Oskari Saarenmaa <os@ohmu.fi> writes: >> On my laptop a simple pgbench run (scale 100, 15 minutes) shows a 1.5% >> performance improvement. > > I would have hoped for a lot better result before anyone would propose > that we should deal with all the portability issues this'll create. > >> A 1.5% performance improvement is small but >> measurable - and IMV more importantly it allows us to drop more than 100 >> lines of backwards (compatible?) code; maybe we could start targeting >> more recent platforms in v10? > > That's basically nonsense: we'll end up adding way more than that to > deal with platforms that haven't got these APIs. I don't understand why you think this would create non-trivial portability issues. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: