-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mail indexing optimization: loading mails & data across multiple days #8599
Labels
performance
performance related issues
Comments
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of processing day-by-day, we can process after we've reached a certain amount. We should still iterate by day, but we instead index multiple days at once. This reduces the number of requests by over 80% on some mailboxes. Closes #8599
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes. Closes #8599
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes, and it may cut loading time in time in such cases. Closes #8599
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes, and it may cut loading time in half in such cases. Closes #8599
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes, and it may cut loading time in half in such cases. Closes #8599
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes, and it may cut loading time in half in such cases. Closes #8599
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes, and it may cut loading time in half in such cases. Closes #8599 Co-authored-by: bir <[email protected]>
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes, and it may cut loading time in half in such cases. Closes #8599 Co-authored-by: bir <[email protected]>
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes, and it may cut loading time in half in such cases. Closes #8599 Co-authored-by: bir <[email protected]>
paw-hub
added a commit
that referenced
this issue
Feb 27, 2025
Instead of indexing day-by-day, we can process after we've reached some threshold. We should still iterate by day, but we should index multiple days at once. This reduces the number of requests by over 80% on some mailboxes, and it may cut loading time in half in such cases. Closes #8599 Co-authored-by: bir <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mail indexing is loading data day-by-day. In #8565 we changed to load
MailSetEntry
s and load them always in full chunks.Unfortunately loading the actual data (
Mail
s,MailDetails
,File
s) is still done day-by-day. It would be more optimal to collect a certain number ofMailSetEntry
s and then execute the download in bigger chunks.Note: there's a similar optimization where we don't write emails to IndexedDB until we've collected a certain number of them.
Test notes
The text was updated successfully, but these errors were encountered: