Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5(EOL), 10.6, 10.11, 11.4, 11.8, 12.3, 13.0
-
Microsoft Windows
-
Related to performance
Description
MDEV-24037 implemented an optimization of the InnoDB specific os_file_flush_func() so that the system library function NtFlushBuffersFileEx() will be invoked when available, instead of the more costly FlushFileBuffers(). These functions are analogous to the POSIX functions fdatasync(2) and fsync(2).
The function my_sync(), which is being used outside InnoDB, is still solely relying on FlushFileBuffers(). To my understanding, this function is being invoked during DDL operations or when a non-default value of sync_binlog=1 (MDEV-16589) is being used.
Attachments
Issue Links
- relates to
-
MDEV-24037 Use NtFlushBuffersFileEx(FLUSH_FLAGS_FILE_DATA_SYNC_ONLY) , the Windows "fdatasync"
-
- Closed
-