2012-01-26, 16:52
I have been using the script as implemented in xperience1080. I love the script but am having some performance issues. I have approximately 11k episodes and 2k movies. Running the script takes about 2.5 minutes each time.
I am wondering if it would be better to have a time parameter to better manage how frequently the script is run. Then the skin could use that as a configurable parameter for the script. If the timestamp was written at the end of the script run, the length of run would become irrelevant to the process because the setting to not run it if it had completed within the last X minutes would still apply.
For those of us with larger libraries, the performance impact is somewhat severe. The script pulls a JSON query for each of the roughly 200 TV shows on my system. If I watch a 3 minute video, watchlist runs upon its completion. This means that I have to wait roughly 2.5 minutes between each video. If you let the user configure the parameter, they take the responsibility of determining how often is too often and how fresh they need the data to be.
I am wondering if it would be better to have a time parameter to better manage how frequently the script is run. Then the skin could use that as a configurable parameter for the script. If the timestamp was written at the end of the script run, the length of run would become irrelevant to the process because the setting to not run it if it had completed within the last X minutes would still apply.
For those of us with larger libraries, the performance impact is somewhat severe. The script pulls a JSON query for each of the roughly 200 TV shows on my system. If I watch a 3 minute video, watchlist runs upon its completion. This means that I have to wait roughly 2.5 minutes between each video. If you let the user configure the parameter, they take the responsibility of determining how often is too often and how fresh they need the data to be.