increase default autocompact threshold "mail.purge_threshhold" from 20mb to 200mb
Categories
(Thunderbird :: General, enhancement)
Tracking
(thunderbird68 verified, thunderbird69 fixed)
People
(Reporter: wsmwk, Assigned: Nomis101)
References
Details
Attachments
(2 files)
3.61 KB,
patch
|
mkmelin
:
review+
|
Details | Diff | Splinter Review |
3.60 KB,
patch
|
jorgk-bmo
:
approval-comm-beta+
|
Details | Diff | Splinter Review |
7 years ago in 2011 we changed the default from 100k to 20MB, a 20,000% increase. Even at that time figures of 100MB and 200MB were proposed. I suggest we look at this again. Personally I use 100MB.
Comment 1•5 years ago
|
||
Thunderbird used to use mail.purge_threshhold, in KB. That was changed to mail.purge_threshhold_mb , in MB. That is why mail.purge_threshold_migrated was created about 7 years ago. I think you have a typo in the title. Most discussions about the threshold seems to be solely about freeing up wasted disk space. It ignores the fact that the number of marked deleted but hidden messages effects the risk of a corrupt folder. I normally get plain text messages with no attachments that average about 10KB. Its unusual for me to get messages larger than 50KB. My main email account has a quota of 1GB. Not everybody is using Gmail and getting HTML messages with large attachments. Whatever values are chosen should be able to accommodate users with different needs, rather than forcing a one size fits all model. The last change in settings raised the minimum setting from 100KB to 1MB and caused me to occasionally have a corrupted inbox in my Fastmail IMAP account. That problem lasted for several years. I don't have a problem with the default value being increased, but the minimum possible setting should not be increased.
Writing a patch for this is very simple, but on what measure does the number depend? On the maximum size of an email the provider allows, the size of the email storage space on the server or something else? Is it important if POP3 or IMAP is used?
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Nomis101 from comment #2) > on what measure does the number depend? ... The total potential space savings across all folders and all accounts, based on all messages deleted in the profile. It is not keyed off any one message size. It covers all account types (except possibly maildir).
Reporter | ||
Comment 4•4 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #3)
(In reply to Nomis101 from comment #2)
on what measure does the number depend? ...
The total potential space savings across all folders and all accounts, based
on all messages deleted in the profile. It is not keyed off any one message
size. It covers all account types (except possibly maildir).
Are you willing to write the patch? I think we only want to change the value if the user hasn't changed it from the default of 20MB, so could base is on part of bug 437657
I think we should increase it to no less than 200MB
Sure, I can write the patch. The only thing I don't know how to do at the moment is
(In reply to Wayne Mery (:wsmwk) from comment #4)
I think we only want to change the value if the user hasn't changed it from the default of 20MB
Need to check this. The value needs to be increased in nsMsgDBFolder.cpp and mailnews.js, right?
Reporter | ||
Comment 6•4 years ago
•
|
||
Correct. The code there (from bug 437657) demonstrates how to check a) if it's still at the default b) if the value (and I guess at that time also the pref name and units) had been migrated.
Reporter | ||
Comment 8•4 years ago
|
||
Looks good to me. Ready to request approval?
Comment 9•4 years ago
|
||
Comment on attachment 9067891 [details] [diff] [review] Patch Review of attachment 9067891 [details] [diff] [review]: ----------------------------------------------------------------- This seems ok to me. Needs some trivial unbitrotting though.
Updated•4 years ago
|
Assignee | ||
Comment 10•4 years ago
|
||
Thanks for the review. Unbitrotted the patch.
Comment hidden (obsolete) |
Updated•4 years ago
|
Comment hidden (obsolete) |
Updated•4 years ago
|
Comment 13•4 years ago
|
||
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/cf23f4f4e5ab
increase default autocompact threshold "mail.purge_threshhold" from 20MB to 200MB. r=mkmelin
Comment 14•4 years ago
|
||
Should we consider this for TB 68?
Reporter | ||
Comment 15•4 years ago
|
||
(In reply to Jorg K (GMT+2) from comment #14)
Should we consider this for TB 68?
Definitely - that is the goal
Updated•4 years ago
|
Comment 16•4 years ago
|
||
TB 68 beta 3:
https://hg.mozilla.org/releases/comm-beta/rev/7d704921878b305c50a9cf912f091a71d3db21ec
Reporter | ||
Comment 17•4 years ago
|
||
v.fixed in beta. Thanks
Reporter | ||
Updated•2 years ago
|
Description
•