Raise auto compaction threshold
Categories
(MailNews Core :: General, task)
Tracking
(thunderbird_esr128 fixed, thunderbird132 fixed, thunderbird133 fixed)
People
(Reporter: darktrojan, Assigned: darktrojan)
References
Details
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
corey
:
approval-comm-beta+
corey
:
approval-comm-release+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
corey
:
approval-comm-esr128+
|
Details | Review |
Assignee | ||
Comment 1•24 days ago
|
||
Updated•24 days ago
|
Assignee | ||
Comment 2•24 days ago
|
||
Updated•24 days ago
|
Comment 3•24 days ago
|
||
Ouch! I am in complete agreement about increasing the threshold because hardware is faster and message stores are bigger. I thought I had filed such a bug, but apparently it was only in my mind.
That said, this in effect increases default threshold by hundred fold? Makes me wonder how responsiveness might be affected at startup - bug 1719072. Shutdown might be less of an issue - bug 1924918
Assignee | ||
Comment 4•24 days ago
|
||
I don't care for the 2000 MB value either, I'm just pointing out all of the places where it needs to be changed. Other people can fight over what the value should be.
Comment 5•23 days ago
|
||
Actually, only "old" users, who had TB prior to the last migration, would have got set back to 20mb?
Anyway, I have no trouble with a default of 1GB or 2G. I think on hardware of the last several years it is a fallacy that having many supershort compacts are on average better than fewer longer ones.
Assignee | ||
Comment 6•23 days ago
|
||
Any new profiles between the raising of the default to 200MB in version 68 and when I removed that code in version 129 would have the value set to 20 MB.
Comment 7•23 days ago
|
||
From the patch ....
It's not only about disk cleaning. We do get occasional complaints that people didn't understand the data is still there on disk even if the "deleted" the message...
It's a fair concern. But I'm thinking:
a) threshold is not the right mechanism to meet those concerns because it cannot be predicted when automatic compact will be triggered (it will depend on message deletion rate and message size, the combination of which could be hours, days or weeks depending on the user), and
b) arbitrarily lowering threshold doesn't best serve the average user.
Users with true privacy concerns about stale data should be doing something like expunge on exit and compact on exit, or doing manual compact at a frequency that meets their privacy needs.
IIRC Gene has been looking at issues around the intersection of expunge and compact?
Comment 8•22 days ago
|
||
Just confirming the esr128 patch apparently works.
I have a profile that always prompted me on startup, suggesting to compact for a 47 MB savings. I had always rejected.
With the patch applied on 128, I'm no longer prompted.
Comment 10•22 days ago
|
||
(In reply to Toby Pilling [:tobyp] from comment #9)
Can this be uplifted?
Geoff already uploaded the ESR variation, so yes, once the first patch lands the ESR version can be uplifted
Comment 11•22 days ago
|
||
Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/d89a215c6235
Raise compaction threshold. r=tobyp,aleca
Assignee | ||
Updated•22 days ago
|
Assignee | ||
Comment 12•21 days ago
|
||
Comment on attachment 9433816 [details]
Bug 1927656 - Raise compaction threshold. r=tobyp,aleca
[Approval Request Comment]
Regression caused by (bug #):
User impact if declined: compact happens too often
Testing completed (on c-c, etc.): it landed yesterday
Risk to taking this patch (and alternatives if risky): low
Comment 13•20 days ago
|
||
Shouldn't the migration have been used as an opportunity to fix the spelling of the pref name mail.purge_threshhold_mb?
Comment 14•20 days ago
|
||
Comment on attachment 9433816 [details]
Bug 1927656 - Raise compaction threshold. r=tobyp,aleca
[Triage Comment]
Approved for beta
Assignee | ||
Comment 15•17 days ago
|
||
Comment on attachment 9433817 [details]
Bug 1927656 - [ESR128] Raise compaction threshold. r=tobyp,aleca
[Approval Request Comment]
Regression caused by (bug #):
User impact if declined: compact happens too often
Testing completed (on c-c, etc.): not long on central, but it can be manually verified
Risk to taking this patch (and alternatives if risky): low
Comment 16•17 days ago
|
||
Comment on attachment 9433817 [details]
Bug 1927656 - [ESR128] Raise compaction threshold. r=tobyp,aleca
[Triage Comment]
Approved for esr128
Comment 17•16 days ago
|
||
bugherder uplift |
Thunderbird 133.0b2:
https://hg.mozilla.org/releases/comm-beta/rev/ed04a298b272
Comment 18•16 days ago
|
||
bugherder uplift |
Thunderbird 128.4.2esr:
https://hg.mozilla.org/releases/comm-esr128/rev/3d6e456da28d
Comment 19•13 days ago
|
||
Comment on attachment 9433816 [details]
Bug 1927656 - Raise compaction threshold. r=tobyp,aleca
[Triage Comment]
Approved for release
Comment 20•10 days ago
|
||
bugherder uplift |
Thunderbird 132.0.1:
https://hg.mozilla.org/releases/comm-release/rev/f3bceb156665
Description
•