We have a modest media library: about 95,000 music files and 1,100 station media files. Our items table has 96,600 rows.
When using the mAirListDB application, there are several nodes in the browse tree that lock up the application’s user interface for 30-60 seconds when they’re clicked. This is disconcerting and I’m geting complaints from our producers.
I’ve scoured the forums and can’t find any report of similar behaviour. I figure that might be because no one find this behaviour to be a problem or that we’re the only users experiencing this behaviour. For now I’m assuming the latter.
I’m curious to know how many items are in the largest browse nodes of other installations.
How long does your mAirListDB take to list a node with 10,000 items?
How do you sub-divide your media collections to keep the items-per-node count to a size that doesn’t impede media management workflows?
Hopefully I’m not the only one who will find the answers to these questions to be interesting. Thanks in advance for sharing your thoughts.