>>>>> "Scott" == Scott Hess <scott@stripped> writes:
Scott> That (storing the blobs out to the filesystem) is the solution we're
Scott> currently pondering. The main downside is that the database is being used
Scott> as the central "memory" for a system that involves a couple components, and
Scott> we'd _really_ rather not teach all components about the off-database blob
Scott> storage, if we can get away with it.
Scott> Does anyone have firm knowledge of the fragmentation differences between
Scott> doing updates and doing a full delete/insert? I can imagine an
Scott> implementation where an update might re-use the currently allocated space,
Scott> so if the updated data is larger than the existing data, fragmentation is
Scott> going to be a problem. But a delete followed by an insert may do better.
Scott> While we can do some measuring to see if this happens, but I'd like to know
Scott> the response of someone with deep knowledge of how MYSQL stores its data.
Yes. MySQL 3.22 will fragment rows if you mix a lot of deletes/inserts into
the same table.
The new ISAM in MySQL 3.23 will automaticly join adjacent deleted
blocks and can extend blocks much better than the old ISAM.
If you can wait a week, I would recommend testing MySQL 3.23 before
starting to hack the source!