From: Tobias Oberstein <tobias.oberstein@gmail.com>
To: Andrey Kuzmin <andrey.v.kuzmin@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: 4x lower IOPS: Linux MD vs indiv. devices - why?
Date: Mon, 23 Jan 2017 22:49:48 +0100 [thread overview]
Message-ID: <14bc36ca-83ea-484e-152b-9856d2e528ac@gmail.com> (raw)
In-Reply-To: <CANvN+ek0DgHF4gFAVep9ygdi=4pi9O9Fp5u3-VOd0iEVCSS0=Q@mail.gmail.com>
Hi Andrey,
> Thanks again for your tips .. the psync thingy in particular. I need to
> verify if that applies to PostgreSQL, because it brings huge gains compared
> to sync!
>
>
> That's easy to explain, it just does one syscall less per IO. It should
> indeed bring home a measurable gain as, with synchronous I/O, I believe
> you're cpu-limited.
Sadly, it seems PostgreSQL currently does lseek/read/write. (I'll double
check tomorrow running perf against an active PostgreSQL instance).
There was a patch discussed here using pread/pwrite when avail
https://www.postgresql.org/message-id/flat/CABUevEzZ%3DCGdmwSZwW9oNuf4pQZMExk33jcNO7rseqrAgKzj5Q%40mail.gmail.com#CABUevEzZ=CGdmwSZwW9oNuf4pQZMExk33jcNO7rseqrAgKzj5Q@mail.gmail.com
which ends with a comment by Tom Lane (PostgreSQL core developer)
"Well, my point remains that I see little value in messing with
long-established code if you can't demonstrate a benefit that's clearly
above the noise level."
=(
I will post the findings from our discussion here to the PG hackers
list. Maybe ...
Cheers,
/Tobias
next prev parent reply other threads:[~2017-01-23 21:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 16:26 4x lower IOPS: Linux MD vs indiv. devices - why? Tobias Oberstein
[not found] ` <CANvN+en2ihATNgrbgzwNXAK87wNh+6jXHinmg2-VmHon31AJzA@mail.gmail.com>
2017-01-23 17:52 ` Tobias Oberstein
[not found] ` <CANvN+em0cjWRnQWccdORKFEJk0OSeQOrZq+XE6kzPmqMPB--4g@mail.gmail.com>
2017-01-23 18:33 ` Tobias Oberstein
2017-01-23 19:10 ` Kudryavtsev, Andrey O
2017-01-23 19:26 ` Tobias Oberstein
2017-01-23 19:13 ` Sitsofe Wheeler
2017-01-23 19:40 ` Tobias Oberstein
2017-01-23 20:24 ` Sitsofe Wheeler
2017-01-23 21:22 ` Tobias Oberstein
[not found] ` <CANvN+emLjb9idri9r42V3W9ia6v0EDGdJYFfhzq6rAuzGWec8Q@mail.gmail.com>
2017-01-23 21:42 ` Andrey Kuzmin
2017-01-23 23:51 ` Tobias Oberstein
2017-01-24 8:21 ` Andrey Kuzmin
2017-01-24 9:28 ` Tobias Oberstein
2017-01-24 9:40 ` Andrey Kuzmin
2017-01-24 22:51 ` Tobias Oberstein
2017-01-25 16:23 ` Elliott, Robert (Persistent Memory)
2017-01-26 17:52 ` Tobias Oberstein
[not found] ` <CANvN+emM2xeKtEgVofOyKri6WBtjqc_o1LMT8Sfawb_RMRXT0g@mail.gmail.com>
2017-01-23 20:10 ` Tobias Oberstein
[not found] ` <CANvN+e=ityWtQj_TJ3yZgTM7mr17VB=3OeyQEEQvdb5tR5AGLA@mail.gmail.com>
[not found] ` <CANvN+emUGQ=voye=E6g4jFRxbp5eS8cGVJb3vTSn-bD5Db2Ycw@mail.gmail.com>
2017-01-23 20:20 ` Tobias Oberstein
[not found] ` <CANvN+e=ASW14ShvY6dmVvUDY3PJVWwY9oQSbOT9EiOnQbSZHzA@mail.gmail.com>
[not found] ` <CANvN+ek0DgHF4gFAVep9ygdi=4pi9O9Fp5u3-VOd0iEVCSS0=Q@mail.gmail.com>
2017-01-23 21:49 ` Tobias Oberstein [this message]
2017-01-23 18:18 ` Kudryavtsev, Andrey O
2017-01-23 18:53 ` Tobias Oberstein
2017-01-23 19:06 ` Kudryavtsev, Andrey O
2017-01-24 9:46 ` Tobias Oberstein
2017-01-24 9:55 ` Tobias Oberstein
2017-01-24 10:03 ` Tobias Oberstein
2017-01-24 15:19 ` Tobias Oberstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14bc36ca-83ea-484e-152b-9856d2e528ac@gmail.com \
--to=tobias.oberstein@gmail.com \
--cc=andrey.v.kuzmin@gmail.com \
--cc=fio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox