If you have any performance data showing problems with internal db
fragmentation (i.e. sqlite3 dbname 'vacuum' fixes it, but cp
doesn't), we'd love to hear about it.
Thanks, Ben, for this informative response. So what you're saying,
in summary is:
1 - Vacuuming on every save is inefficient to the point of silliness.
2 - For anything but very large databases and/or running on slow
hardware, the benefits of vacuuming is minimal anyway.
To that, I pose another question: Why, then, does it make such a
huge difference when I run the vacuum command against Mail's database?
After just a month of usage, Mail seems sluggish when switching
between various folders, but once I run the vacuum command, it is once
again snappy?
Incidentally, it was the Mail vacuum trick that prompted me to
check into this to begin with. You may thank b.bum. :-)
--
I.S.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
