>so you could see for instance, your DB filesize vs all users avg >filesize who had within 100 tracks or so what you had numberwise. > That's never going to work well - it would be a meaningless number. The same set of tracks loaded on different machines could give a different DB size, due to many reasons. filepaths can be different, SBS version could cause differences, a DB filesize could be bigger than actually needed due to the way it allocates space. A lot of users wouldn't opt in; so the average would be over the set of users that are likely to opt in.
Twice the expected size wouldn't mean there's a problem. Eg. some people have Album Artist tags for everything, some people don't. Some people have MusicBrainz tags, others don't. Some people have large comment tags, lyrics tags, etc. I have plugins that store a lot of extra data in the DB. So, my DB size may be a lot greater than other users without those plugins. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
