Starting 'delayed message expunge' on a large Cyrus 2.3.16 server.

[Eric Luyten]

On Fri, May 13, 2011 3:25 pm, Sebastian Hagedorn wrote:
> --On 13. Mai 2011 14:57:36 +0200 Eric Luyten <Eric.Luyten at vub.ac.be> wrote:
>
>
>> I currently have the following entry in my cyrus.conf :
>>
>>
>> delprune	cmd="cyr_expire -E 1" at=0055
>>
>> which takes about six minutes, every night, to
>>
>> May 13 00:55:11 cyr_expire[21210]: Expunged 0 out of 0 messages from 0
>> mailboxes May 13 00:55:11  cyr_expire[21210]: duplicate_prune: pruning back 1
>>  days    May 13 01:01:45cyr_expire[21210]: duplicate_prune: purged 205245
>> out of 401016 entries
>>
>>
>> I think I'll have to launch several cyr_expire's one after another or in
>> parallel (will be done during night hours or weekends) to get the job done
>> before production load arrives.
>
> We have a setup similar to yours in size and get by just fine with only
> this entry:
>
> delprune	cmd="cyr_expire -E 3 -X 3 -D 3" at=0400
>
> I just checked our logs. It usually finishes around 7 am.


Sebastian,


I just ran, during office hours, a 'cyr_expire' against our mailboxes
with names starting with 'user.t' (3.3 % of almost 475.000 mailboxes)
and this took under six minutes elapsed time.
Since all it did was detect there are no 'cyrus.expunge' files present,
it did not have to carry out the physical pruning, of course.

We're almost certainly not an order of magnitude off from your figures,
it appears, but more tests are sitting in our pipeline.


Thank you for your earlier feedback,
Eric Luyten, Computing Centre VUB/ULB.