adamslim wrote: > It's just the web interface, and especially when I'm doing more complex > stuff with custom browse. Some of the database queries can take over > 20-30s, and since I would like to run several queries (for example, > first to get piano music, then instrumental rather than orchestral), it > makes the whole browsing system less of a joy than it should be.
30 seconds per thing is way too slow for happy users. I have not looked at the way SBS talks to MySql recently (i.e. not in years). But in my 30+ years of optimizing systems using DBMS, the rules are nearly always the same. 1) create proper index structures so that you don't have to do table scans. 2) don't do four, five, or eight way joins. Sure, they are handy, but they don't scale and are always too slow. If you are doing a lot of custom browsing that does a lot of sql queries, I'd start there. While my collection is less than half the size of yours, ~800 artists, 10,000 songs, the DB is tiny. only about 220K I know that MySql will attempt to cache tables into memory, and with a 4GB machine, it all should be in memory all the time. -- Pat Farrell http://www.pfarrell.com/ _______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
