Re: [HACKERS] lseek/read/write overhead becomes visible at scale .. - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..
Date
Msg-id 20170124183613.cbb47nqbvso4rvjb@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..  (Tobias Oberstein <tobias.oberstein@gmail.com>)
Responses Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..  (Andres Freund <andres@anarazel.de>)
Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..  (Tobias Oberstein <tobias.oberstein@gmail.com>)
List pgsql-hackers
Tobias Oberstein wrote:

> I am benchmarking IOPS, and while doing so, it becomes apparent that at
> these scales it does matter _how_ IO is done.
> 
> The most efficient way is libaio. I get 9.7 million/sec IOPS with low CPU
> load. Using any synchronous IO engine is slower and produces higher load.
> 
> I do understand that switching to libaio isn't going to fly for PG
> (completely different approach).

Maybe it is possible to write a new f_smgr implementation (parallel to
md.c) that uses libaio.  There is no "seek" in that interface, at least,
though the interface does assume that the implementation is blocking.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tobias Oberstein
Date:
Subject: Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..
Next
From: Corey Huinker
Date:
Subject: Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)