[
https://issues.apache.org/jira/browse/IGNITE-29175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134200#comment-18134200
]
Ignite TC Bot commented on IGNITE-29175:
----------------------------------------
{panel:title=Branch: [pull/13710/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13710/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9452841&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9452841
rerunBuildIds=9453954,9453956,9453958,9453960,9453962{color}
> Copy compressed snapshot partitions sparsely on restore instead of punching
> holes
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-29175
> URL: https://issues.apache.org/jira/browse/IGNITE-29175
> Project: Ignite
> Issue Type: Improvement
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Major
> Fix For: 2.19
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Partition files of a compressed cache group are sparse: each page keeps only
> its compressed bytes,
> the rest of the page is a hole.
>
> When such a group is restored from a snapshot, every partition goes through
> two passes:
> - the file is copied as a dense file, so the holes turn into zeros on disk;
> - the copy is read again page by page, and a hole is punched after each page
> with a separate fallocate call.
> On a store with many partitions this makes the restore much slower than
> creating the same snapshot.
>
> The copy can write only the compressed bytes of each page instead: the file
> system leaves the rest
> of the page unallocated, and the second pass is not needed.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
