[jira] [Updated] (IGNITE-22664) Write intensive aipersist checkpoints
[ https://issues.apache.org/jira/browse/IGNITE-22664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Pligin updated IGNITE-22664: - Epic Link: IGNITE-22685 > Write intensive aipersist checkpoints > - > > Key: IGNITE-22664 > URL: https://issues.apache.org/jira/browse/IGNITE-22664 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Philipp Shergalis >Priority: Major > Labels: ignite-3 > > Inserting 1 million rows, resulting database after compaction takes around > 330MB on the disk. Still, delta files created in the process sum up to 3.3 > gigabytes (checked by disabling compaction code, 256 MB region size, 16KB > page size), so checkpointing and compacting can't keep up with > write-intensive scenarios. We should try to optimise amount of writing to disk > > Also, RocksDB with 1 million rows used only 95MB of disk space -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22664) Write intensive aipersist checkpoints
[ https://issues.apache.org/jira/browse/IGNITE-22664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis updated IGNITE-22664: --- Description: Inserting 1 million rows, resulting database after compaction takes around 330MB on the disk. Still, delta files created in the process sum up to 3.3 gigabytes (checked by disabling compaction code, 256 MB region size, 16KB page size), so checkpointing and compacting can't keep up with write-intensive scenarios. We should try to optimise amount of writing to disk Also, RocksDB with 1 million rows used only 95MB of disk space was: Inserting 1 million rows, resulting database after compaction takes around 330MB on the disk. Still, delta files created in the process sum up to 3.3 gigabytes (checked by commenting out compaction code, 256 MB region size), so checkpointing and compacting can't keep up with write-intensive scenarios. We should try to optimise amount of writing to disk Also, RocksDB with 1 million rows used only 95MB of disk space > Write intensive aipersist checkpoints > - > > Key: IGNITE-22664 > URL: https://issues.apache.org/jira/browse/IGNITE-22664 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Philipp Shergalis >Priority: Major > Labels: ignite-3 > > Inserting 1 million rows, resulting database after compaction takes around > 330MB on the disk. Still, delta files created in the process sum up to 3.3 > gigabytes (checked by disabling compaction code, 256 MB region size, 16KB > page size), so checkpointing and compacting can't keep up with > write-intensive scenarios. We should try to optimise amount of writing to disk > > Also, RocksDB with 1 million rows used only 95MB of disk space -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22664) Write intensive aipersist checkpoints
[ https://issues.apache.org/jira/browse/IGNITE-22664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Shergalis updated IGNITE-22664: --- Summary: Write intensive aipersist checkpoints (was: Insanely memory consuming checkpoints in aipersist) > Write intensive aipersist checkpoints > - > > Key: IGNITE-22664 > URL: https://issues.apache.org/jira/browse/IGNITE-22664 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Philipp Shergalis >Priority: Major > Labels: ignite-3 > > Inserting 1 million rows, resulting database after compaction takes around > 330MB on the disk. Still, delta files created in the process sum up to 3.3 > gigabytes (checked by commenting out compaction code, 256 MB region size), so > checkpointing and compacting can't keep up with write-intensive scenarios. We > should try to optimise amount of writing to disk > > Also, RocksDB with 1 million rows used only 95MB of disk space -- This message was sent by Atlassian Jira (v8.20.10#820010)
