> > Lots of room for optimization. > Optimisation is an ingoing process, and not applicable as a bug report unless there is a specific benchmark to be achieved. A goal without a specific, measurable result is of dubious value.
The optimise process is simply a call for mysql to "optimise" the tables. Even with no 'new data', there is manipulation. I would also be curious as to how much activity the db is seeing not from scans, but from general use: ratings updates, play counts, this-party plugin activity etc. All of these would have an effect on the db and may play into the time taken for mysql to "OPTIMIZE TABLE tracks;" However, as a fun investigation, try making schema_optimize.sql an empty file and see what happens. It should certainly save time, but the result on the db would probably depend on the contents of the db. This sql file not only optimises tables, but rebuilds the contributor_albums in response to bug 4882. -kdf _______________________________________________ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
