Re: Use pread and pwrite instead of lseek + write and read - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Use pread and pwrite instead of lseek + write and read
Date
Msg-id 7109.1471441241@sss.pgh.pa.us
Whole thread Raw
In response to Use pread and pwrite instead of lseek + write and read  (Oskari Saarenmaa <os@ohmu.fi>)
Responses Re: Use pread and pwrite instead of lseek + write and read  (Oskari Saarenmaa <os@ohmu.fi>)
Re: Use pread and pwrite instead of lseek + write and read  (Robert Haas <robertmhaas@gmail.com>)
Re: Use pread and pwrite instead of lseek + write and read  (Claudio Freire <klaussfreire@gmail.com>)
List pgsql-hackers
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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Why we lost Uber as a user
Next
From: Tom Lane
Date:
Subject: Re: drop src/backend/port/darwin/system.c ?