Quit out of Mail, open a terminal window and run:
When it’s done you should notice a huge improvement in speed on Mail.app startup at least.
The article and comments claim disk savings too, however prior to running the database file was 31MB and after 28MB, the speed increase made it worth it.
2 Comments so far
Leave a comment
Fields in bold are required. Email addresses are never published or distributed.
Some HTML code is allowed:<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
URLs must be fully qualified (eg: http://blogs.sackheads.org/hide),and all tags must be properly closed.
Line breaks and paragraphs are automatically converted.
Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.
Welcome to Shawn Sorichetti.I am hide.
FYI: http://www.sqlite.org/lang_vacuum.html and check out the auto_vacuum link. (edit to display properly)
I’m somewhat surprised that there isn’t a ‘vacuum when the sparsity gets to X%’ or similar. Having said that, it took maybe a minute to vacuum to run the command for me and much longer for another friend, do you think the average user would be happy with “Please wait, optimising database” at startup or shutdown?
I think because it’s not run at all, that when you and your other friend ran it, it took longer. If it were run on a regular basis I don’t think it would take so long.
I don’t think it needs to run every startup or every shutdown, more like an fsck, if not run in x amount of days, run it.