Guidelines
Steps to reproduce
- Keep a large collection of ~70k images all inside a single folder → the app is smooth (browsing, moving, copying, deleting, opening settings all feel fine).
- Organize the exact same images into a deep folder structure, ending up with ~4k folders (i.e. ~4k albums), same total item count.
- Use the app normally: launch it, open the Albums page, open/change a setting, or move/copy/delete an image.
Expected results
Since the total number of items is unchanged, performance should stay roughly the same regardless of how the items are distributed across folders.
Actual results
With ~4k albums the app becomes sluggish almost everywhere: launching, opening the Albums page, entering settings, changing a setting, and moving/copying/deleting/opening images all take noticeably longer. The delay grows with the number of albums, and is unrelated to the number of items (same 70k items are fine as a single folder).
I've confirmed this isn't Android media indexing — I waited for indexing to fully complete before testing, and a nested folder structure is actually faster than a single flat folder at the OS/file level. So the slowdown seems specific to how the app derives album data.
Since the effect tracks album count rather than item count, I suspect it comes from the per-album aggregation done over the whole entry list (e.g. finding each album's cover/recent entry and per-album counts appear to scan all entries once per album), possibly combined with summary caches being cleared fairly broadly after edits. I may well be wrong on the details — just flagging the pattern in case it's useful.
Screenshots or Video
N/A
Logs
aves-logs-20260721_162338.txt
Custom environment
Additional context
No response
Guidelines
Steps to reproduce
Expected results
Since the total number of items is unchanged, performance should stay roughly the same regardless of how the items are distributed across folders.
Actual results
With ~4k albums the app becomes sluggish almost everywhere: launching, opening the Albums page, entering settings, changing a setting, and moving/copying/deleting/opening images all take noticeably longer. The delay grows with the number of albums, and is unrelated to the number of items (same 70k items are fine as a single folder).
I've confirmed this isn't Android media indexing — I waited for indexing to fully complete before testing, and a nested folder structure is actually faster than a single flat folder at the OS/file level. So the slowdown seems specific to how the app derives album data.
Since the effect tracks album count rather than item count, I suspect it comes from the per-album aggregation done over the whole entry list (e.g. finding each album's cover/recent entry and per-album counts appear to scan all entries once per album), possibly combined with summary caches being cleared fairly broadly after edits. I may well be wrong on the details — just flagging the pattern in case it's useful.
Screenshots or Video
N/A
Logs
aves-logs-20260721_162338.txt
Custom environment
Additional context
No response