[MDEV-26029] Sparse files are inefficient on thinly provisioned storage - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5(EOL), 10.6
Fix Version/s: 10.6.3
Component/s: Storage Engine - InnoDB
Labels:
- performance

Description

The MariaDB implementation of page_compressed tables for InnoDB uses sparse files. In the worst case, in the data file, every data page will consist of some data followed by a hole. This may be extremely inefficient in some file systems.

If the underlying storage device is thinly provisioned (can compress data on the fly), it would be good to write regular files (with sequences of NUL bytes at the end of each page_compressed block) and let the storage device take care of compressing the data.

Attachments

Issue Links

blocks

MDEV-11068 Review which innodb_compression_algorithm to support in binary packages

Closed

is blocked by

MDEV-26042 Atomic write capability is not detected correctly

Closed

relates to

MDEV-26192 Sparse files are being created on thinly provisioned storage

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2021-06-28 09:51

Updated:: 2021-07-20 14:36

Resolved:: 2021-06-29 12:29

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

1d 0.75h

Git Integration

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