Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 546221" data-attributes="member: 10858">Sometimes huge data amounts aren't possible to be handled with &quot;real-time&quot; queries but instead you need to take a different approach and turn the responsibilities upside down. Instead of generating the results always on the fly it could be possible to generate that data only when inserting new data (importing a new movie) to the database. I'm not sure how Moving Pictures handles the current situation and not sure how easy such different approach would be, would it be even possible (some categories can be build based on the watched status? So it would require MP plugin side to do DB updates for categories). But in general that is pretty good way to improve performance to a different level (with especially good scalability as the UI wont create x*y*z... like queries where the performance drops radically when data amounts increase). Unfortunately it works only if the data is pretty static, meaning that application side wont do that much changes into it.This is what was done for the EPG pretty recently, as in the worst case there could have been few second delays for a button press as the SQL queries needed to be run for the huge amount of EPG data (with complex recording rules).</blockquote>

[QUOTE="tourettes, post: 546221, member: 10858"] Sometimes huge data amounts aren't possible to be handled with "real-time" queries but instead you need to take a different approach and turn the responsibilities upside down. Instead of generating the results always on the fly it could be possible to generate that data only when inserting new data (importing a new movie) to the database. I'm not sure how Moving Pictures handles the current situation and not sure how easy such different approach would be, would it be even possible (some categories can be build based on the watched status? So it would require MP plugin side to do DB updates for categories). But in general that is pretty good way to improve performance to a different level (with especially good scalability as the UI wont create x*y*z... like queries where the performance drops radically when data amounts increase). Unfortunately it works only if the data is pretty static, meaning that application side wont do that much changes into it. This is what was done for the EPG pretty recently, as in the worst case there could have been few second delays for a button press as the SQL queries needed to be run for the huge amount of EPG data (with complex recording rules). [/QUOTE]

Verification