maria-discuss team mailing list archive
Mailing list archive
Jure Sah <dustwolfy@xxxxxxxxx>
Sat, 7 Sep 2019 20:27:48 +0200
addr=dustwolfy@xxxxxxxxx; prefer-encrypt=mutual; keydata= xsDiBEeAIR4RBACeK+DmRvplI84UZZWOzcT0ZSrpAQu+4qiBkLIrYIBwMJ0m2SH/me2lSu4E JeW3OkF29R12Bjmk4QQNjQH6LPSSjc1EIud0BKfCGIZHqUsJZdeoevhtviZ86K7+FNxpnnLY w06iTy6keDzhMKI5T5Xyd8ir2bBud2ze4HYax0Ij/wCgyJI6i0XWW6KMGFSh+SmpRNUs3P8D /0jd6tutbBkGY7UbbJidSt8PVSZGTq/gI6LB8TYnzFEnqgvsgGXITaTBPXEiJ4cj6nl4y1Qr qH139wn25fxLtJt2iVzSUUn9Cg2OQ8kxjn/50AdCRMTnIMGCG1YUmALRimlM9BPRGkdPdiso Lyfya5Z/uLqHF7h0zZHOPPXh+mtPA/9TuafdwGDCq3+hLa5JUSkxS8P4JCBs/oHC6Dlsp7pE K0icUFJC1huY/slQMYTWOi/Zj5dAPf2mRzjuIYm/mCb5Yu9lrsZXeel8Z1iEkR3VDaQOCZST U8DnjRAi5/NDeSxXaFHgVXxwNjYmyyHw52xK6CPnWqmiVlcHg35a2u/Nwc0eSnVyZSBTYWgg PGR1c3R3b2xmeUBnbWFpbC5jb20+wmAEExECACAFAkeAIR4CGwMGCwkIBwMCBBUCCAMEFgID AQIeAQIXgAAKCRAHqY1ld73eqIo0AKC8hlliVKpZpx+OPsPimj1LK70xAwCeJuX5i9yOXG12 I9sgfLIy+PDDftbOwU0ER4AhKRAIALfBqKBw7oF4Spa6/7WQC41/VaLb2CG82flM/UiMk/6p XyrdxfV5EKLExsCdyx1cPfyAy3fDUf2MHSTuzpoUFzqDJ7KdnIeGSHr+KNNhxHbmkGaovfJN K9F1v40VpLDG5TrxZpAPNn4KnaclqhiBIyaHKyK96EbkVxlMuN7WGQv9ePpBNhuZHByEqLJB bYAlCeWt/iFXhkivxC8NkSX221dJBmBdj2qW0ZicHtQO7xaf8mR1A1o6QHnICLgTpdfyRjR0 OB3WrR73oDwMNEurigJzb0+b3bUj7b+jX+gdpn8IOco/8J5PijQ3E1ef44gFSJnmW96AJcq8 yRFGw+sNiHcABA0IAJWYufcelH2WfA0EBJHnOB++Nmt+GZYBykuEGIJmVDCICTr7fHJ/MMst a0W9Fw4fzK4DTKa7RhW7UQJVJK7k3g3an2TYX2IHtLavnuohUx1QRYe4N0uIPZkFZ7HXFtBE s6Q2MlIWXCGPAFyxHTROyiZ2Bsq8EPbChm1HOxNasBEp/SMROtqjQesVLK229/g8h2x1GtuO 2DvPeeuj19oUDhZUZpI4sg+Jv/ytYwxV2Yp9CWMjgWy8+b9nTjtn/8X3ck05TjhHiOms0IG5 Mzo66vp5uexGJCD/yQ+3wpSZk/iw64TfsclVfOxg4g15a9SMxUneTvXr9UqmMMa4AdwwpNLC SQQYEQIACQUCR4AhKQIbDAAKCRAHqY1ld73eqA7lAJ9XIIcETBf2oqUcPRV31muoKrDZVQCg gv+WprErmiEH9omLetmhy2JzBcY=
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
It would appear that on a typical webserver, the majority of disk i/o
belongs to the MariaDB database process. It would appear it's mostly
waiting on fsync(), which to my understanding is executed at least once
I understand that this is extensively researched in the documentation
and it has to do with the recovery of data in case of an unexpected
The thing is, this has many performance issues because it caps database
performance at whatever the speed of the underlying physical storage is,
even if the changed data fits into the available RAM. It also results in
the circumstance where if anything is impacting performance of the
storage system on the server, this will break MariaDB and cause the
service to go offline (time out), even if there is sufficient RAM in the
machine to continue operating as normal from page cache.
In a typical scenario you have a website which is writing things like
session and page cache data which expires within an hour and would be no
great loss if missing from a backup. Especially if the volume of the
missing data would be 30 seconds (kernel default for committing dirty
pages to disk) and mind you this setting is configurable.
Temporary tables cannot be used in this case, because they are deleted
as soon as the session ends, which is too soon.
Is there a different solution that could be used here?
I've also noticed in the documentation that the options to control fsync
usage are even more limited than in the MySQL server. They are also very
strongly argued against. Considering the point that InnoDB is considered
to be in an inconsistent state in any event, so long as the server is
not cleanly stopped, is there really justification for such strong
Disabling fsync boosts performance of a typical MySQL server by
something like a factor of 3.
Description: OpenPGP digital signature