2012-09-18, 20:00
Just a query, but one of the biggest frustrations left in the UX is the significant delay when entering the Movie library (or when returning to the Movie library having finished watching a movie). For the Pi, it's a definite scalability issue due to the limited processing ability of the CPU.
I've got over 500 movies in my library, all stored in MySQL so there should be no need to access NFS/SMB/etc. - just pull in the metadata with SQL queries, and hit the local thumbnail cache on SD card - yet the delay to display the Movie library is approaching 30 seconds before the first 8 thumbnails appear... is the Pi having to parse *every* movie in the library just to display the 8 that are currently in view? Is there any way to make this process more efficient, perhaps querying subsets of movie data based on where the user is within the library (a cursor moving through the data, as it were)?
I've got over 500 movies in my library, all stored in MySQL so there should be no need to access NFS/SMB/etc. - just pull in the metadata with SQL queries, and hit the local thumbnail cache on SD card - yet the delay to display the Movie library is approaching 30 seconds before the first 8 thumbnails appear... is the Pi having to parse *every* movie in the library just to display the 8 that are currently in view? Is there any way to make this process more efficient, perhaps querying subsets of movie data based on where the user is within the library (a cursor moving through the data, as it were)?
