Disable timeline cleanup mechanisms that are no longer necessary

Element's new timeline alg should keep is free from timeline loops and
empty chunks.
Thus, removing these checks should give us back a little bit of faster
room loading.

Change-Id: I7c6bc314b98410dd47af44e958422860f26771ce
This commit is contained in:
SpiritCroc 2022-09-17 17:23:46 +02:00
parent 991a658221
commit 7d4c489816
1 changed files with 4 additions and 8 deletions

View File

@ -60,14 +60,10 @@ import java.util.concurrent.atomic.AtomicReference
* Once we got a ChunkEntity we wrap it with TimelineChunk class so we dispatch any methods for loading data. * Once we got a ChunkEntity we wrap it with TimelineChunk class so we dispatch any methods for loading data.
*/ */
// Whether to search for timeline loops, and fix them. // [No longer necessary] Whether to search for timeline loops, and fix them.
// TODO: once we feel comfortable that this is no longer necessary, const val ENABLE_TIMELINE_LOOP_SPLITTING = false
// we probably want to disable this again for improving performance. // [No longer necessary] Whether to search for stuck timelines due to empty self-linking chunks.
const val ENABLE_TIMELINE_LOOP_SPLITTING = true const val ENABLE_TIMELINE_EMPTY_CHUNK_CLEANUP = false
// Whether to search for stuck timelines due to empty self-linking chunks.
// TODO: once we feel comfortable that this is no longer necessary,
// we probably want to disable this again for improving performance.
const val ENABLE_TIMELINE_EMPTY_CHUNK_CLEANUP = true
// Performance consideration for huge timelines, when having ENABLE_TIMELINE_LOOP_SPLITTING or ENABLE_TIMELINE_EMPTY_CHUNK_CLEANUP set to true // Performance consideration for huge timelines, when having ENABLE_TIMELINE_LOOP_SPLITTING or ENABLE_TIMELINE_EMPTY_CHUNK_CLEANUP set to true
const val MAX_CHUNK_REPAIR_CHECK_COUNT = 100 const val MAX_CHUNK_REPAIR_CHECK_COUNT = 100