Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-21382

use fdatasync() for redo log where appropriate

Details

    Description

      Redo log files are fixed size files. They're almost never renamed. So, metadata is not changed. For such cases we can use `fdatasync()` which doesn't flush metadata, like `fsync()` does. That should bring use some performance.

      Attachments

        Issue Links

          is blocked by

          Task - A task that needs to be done. MDEV-18115 Remove dummy tablespace for the redo log

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-14425 Change the InnoDB redo log format to reduce write amplification

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Task - A task that needs to be done. MDEV-22177 more fsync() -> fdatasync() in InnoDB

          • Major - Major loss of function.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Eugene Kosov (Inactive) made transition -
            Open Closed
            		13d 23h 49m 1

            People

              kevg Eugene Kosov (Inactive)
              kevg Eugene Kosov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.