From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: "Bhatnagar, Rishabh" <risbhat@amazon.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
abuehaze@amazon.com
Subject: Re: EXT4 IOPS degradation between 4.14 and 5.10
Date: Wed, 8 Feb 2023 14:37:30 -0500 [thread overview]
Message-ID: <Y+P5+jrsZOjqG+VT@mit.edu> (raw)
In-Reply-To: <20230208140247.rt62xdtriopfdb4o@quack3>
On Wed, Feb 08, 2023 at 03:02:47PM +0100, Jan Kara wrote:
> > I believe its the MySQL database though not so sure.
>
> Well, in that case I think your MySQL DB is somewhat misconfigured. At
> least as far as we have been consulting MySQL / MariaDB developers
> regarding benchmarking, they suggested we should configure the database to
> use direct IO and increase DB internal buffers instead of relying on
> buffered IO and pagecache behavior. And if your fio job is representative
> of the IO load the DB really creates, I'd agree that that would be a saner
> and likely more performant configuration ;)
Could it possibly be Postgres? I happen to know that Amazon RDS and
Google Cloud SQL support both MySQL and Postgres, and there are some
optimizations that some of us in the Cloud space have been pursuing
which are much easier because MySQL uses Direct I/O, but unfortunately
Postgres uses buffered I/O and doens't support DIO. :-(
- Ted
prev parent reply other threads:[~2023-02-08 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 0:33 EXT4 IOPS degradation between 4.14 and 5.10 Bhatnagar, Rishabh
2023-01-26 9:32 ` Jan Kara
2023-01-26 18:23 ` Bhatnagar, Rishabh
2023-01-27 12:17 ` Jan Kara
2023-01-30 17:45 ` Bhatnagar, Rishabh
2023-02-08 14:02 ` Jan Kara
2023-02-08 19:17 ` Bhatnagar, Rishabh
2023-02-09 8:34 ` Jan Kara
2023-02-08 19:37 ` Theodore Ts'o [this message]
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=Y+P5+jrsZOjqG+VT@mit.edu \
--to=tytso@mit.edu \
--cc=abuehaze@amazon.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=risbhat@amazon.com \
/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;
as well as URLs for NNTP newsgroup(s).