home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Plugin Development
SQLiteDatabase Plugin for MP2
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MJGraf" data-source="post: 1028066" data-attributes="member: 17886"><p>Now the interesting part - the first results from Read Test 1.</p><p>What I did is as I said I did a completely fresh import of my test music collection restarted the MP2 Server and executed the search as described above:</p><p></p><p><u>Import / Restart MP2 Server / Read Test 1:</u></p><p>SQL1 (Genres): 1ms</p><p>SQL2 (AudioLanguages): 1ms</p><p>SQL3 (Actors): 2ms</p><p>SQL4 (Directors): 1ms</p><p>SQL5 (Writers): 1ms</p><p>SQL6 (Artists): 308ms</p><p>SQL7 (Genres): 25ms</p><p>SQL8 (Albumartist): 61ms</p><p>SQL9 (Composers): 116ms</p><p>SQL10 (Episode): 1ms</p><p>SQL11 (DVDEpisode): 1ms</p><p>SQL12 (Mediaitem): 94ms</p><p></p><p>As you can see, the important queries here are SQL6 (Artists), SQL7 (Genres), SQL8 (Albumartist), SQL9 (Composers) and SQL12 (Mediaitem). This is expected since these are dealing with music - the other queries deal with videos, movies, etc. which are not in my database. These relevant SQL queries take in total about 0.6 seconds, which is relatively long IMO, but it is not extreeeeemly long so that it renders MP2 unusable.</p><p>To verify my results, I restarted the server and executed the same search again.</p><p></p><p><u>Restart MP2 Server / Read Test 1:</u></p><p>SQL1 (Genres): 1ms</p><p>SQL2 (AudioLanguages): 1ms</p><p>SQL3 (Actors): 1ms</p><p>SQL4 (Directors): 1ms</p><p>SQL5 (Writers): 1ms</p><p>SQL6 (Artists): 482ms</p><p>SQL7 (Genres): 25ms</p><p>SQL8 (Albumartist): 64ms</p><p>SQL9 (Composers): 116ms</p><p>SQL10 (Episode): 1ms</p><p>SQL11 (DVDEpisode): 1ms</p><p>SQL12 (Mediaitem): 80ms</p><p></p><p>Now the relevant SQL queries took in total about 0.77 seconds, which I thought was just a measuring inaccuracy. So I restarted the MP2 Server and did the test again. And now the magic happened:</p><p></p><p><u>Restart MP2 Server / Read Test 1:</u></p><p>SQL1 (Genres): 1ms</p><p>SQL2 (AudioLanguages): 1ms</p><p>SQL3 (Actors): 1ms</p><p>SQL4 (Directors): 1ms</p><p>SQL5 (Writers): 0ms</p><p>SQL6 (Artists): 80ms</p><p>SQL7 (Genres): 19ms</p><p>SQL8 (Albumartist): 53ms</p><p>SQL9 (Composers): 93ms</p><p>SQL10 (Episode): 1ms</p><p>SQL11 (DVDEpisode): 1ms</p><p>SQL12 (Mediaitem): 55ms</p><p></p><p>All of a sudden, the search only took 0.3 seconds. I couldn't believe it and did the Read Test 1 two more times:</p><p></p><p><u>Restart MP2 Server / Read Test 1:</u></p><p>SQL1 (Genres): 1ms</p><p>SQL2 (AudioLanguages): 1ms</p><p>SQL3 (Actors): 0ms</p><p>SQL4 (Directors): 1ms</p><p>SQL5 (Writers): 1ms</p><p>SQL6 (Artists): 81ms</p><p>SQL7 (Genres): 20ms</p><p>SQL8 (Albumartist): 52ms</p><p>SQL9 (Composers): 93ms</p><p>SQL10 (Episode): 1ms</p><p>SQL11 (DVDEpisode): 1ms</p><p>SQL12 (Mediaitem): 56ms</p><p></p><p><u>Restart MP2 Server / Read Test 1:</u></p><p>SQL1 (Genres): 1ms</p><p>SQL2 (AudioLanguages): 1ms</p><p>SQL3 (Actors): 1ms</p><p>SQL4 (Directors): 1ms</p><p>SQL5 (Writers): 1ms</p><p>SQL6 (Artists): 80ms</p><p>SQL7 (Genres): 20ms</p><p>SQL8 (Albumartist): 53ms</p><p>SQL9 (Composers): 94ms</p><p>SQL10 (Episode): 1ms</p><p>SQL11 (DVDEpisode): 1ms</p><p>SQL12 (Mediaitem): 55ms</p><p></p><p>As you can see, now the measurements were more or less constant at about 0.3 seconds. The last test I did so far was just doing Read Test 1 again, but this time without restarting the MP2 Server - and again the result was more or less the same:</p><p><u></u></p><p><u>Read Test 1:</u></p><p>SQL1 (Genres): 1ms</p><p>SQL2 (AudioLanguages): 1ms</p><p>SQL3 (Actors): 1ms</p><p>SQL4 (Directors): 1ms</p><p>SQL5 (Writers): 1ms</p><p>SQL6 (Artists): 78ms</p><p>SQL7 (Genres): 20ms</p><p>SQL8 (Albumartist): 55ms</p><p>SQL9 (Composers): 93ms</p><p>SQL10 (Episode): 1ms</p><p>SQL11 (DVDEpisode): 1ms</p><p>SQL12 (Mediaitem): 64ms</p><p></p><p>And I already have a suspicion where this comes from - maybe a first hook to implement an optimization.</p><p>More about it tomorrow...</p><p></p><p>Michael</p></blockquote><p></p>
[QUOTE="MJGraf, post: 1028066, member: 17886"] Now the interesting part - the first results from Read Test 1. What I did is as I said I did a completely fresh import of my test music collection restarted the MP2 Server and executed the search as described above: [U]Import / Restart MP2 Server / Read Test 1:[/U] SQL1 (Genres): 1ms SQL2 (AudioLanguages): 1ms SQL3 (Actors): 2ms SQL4 (Directors): 1ms SQL5 (Writers): 1ms SQL6 (Artists): 308ms SQL7 (Genres): 25ms SQL8 (Albumartist): 61ms SQL9 (Composers): 116ms SQL10 (Episode): 1ms SQL11 (DVDEpisode): 1ms SQL12 (Mediaitem): 94ms As you can see, the important queries here are SQL6 (Artists), SQL7 (Genres), SQL8 (Albumartist), SQL9 (Composers) and SQL12 (Mediaitem). This is expected since these are dealing with music - the other queries deal with videos, movies, etc. which are not in my database. These relevant SQL queries take in total about 0.6 seconds, which is relatively long IMO, but it is not extreeeeemly long so that it renders MP2 unusable. To verify my results, I restarted the server and executed the same search again. [U]Restart MP2 Server / Read Test 1:[/U] SQL1 (Genres): 1ms SQL2 (AudioLanguages): 1ms SQL3 (Actors): 1ms SQL4 (Directors): 1ms SQL5 (Writers): 1ms SQL6 (Artists): 482ms SQL7 (Genres): 25ms SQL8 (Albumartist): 64ms SQL9 (Composers): 116ms SQL10 (Episode): 1ms SQL11 (DVDEpisode): 1ms SQL12 (Mediaitem): 80ms Now the relevant SQL queries took in total about 0.77 seconds, which I thought was just a measuring inaccuracy. So I restarted the MP2 Server and did the test again. And now the magic happened: [U]Restart MP2 Server / Read Test 1:[/U] SQL1 (Genres): 1ms SQL2 (AudioLanguages): 1ms SQL3 (Actors): 1ms SQL4 (Directors): 1ms SQL5 (Writers): 0ms SQL6 (Artists): 80ms SQL7 (Genres): 19ms SQL8 (Albumartist): 53ms SQL9 (Composers): 93ms SQL10 (Episode): 1ms SQL11 (DVDEpisode): 1ms SQL12 (Mediaitem): 55ms All of a sudden, the search only took 0.3 seconds. I couldn't believe it and did the Read Test 1 two more times: [U]Restart MP2 Server / Read Test 1:[/U] SQL1 (Genres): 1ms SQL2 (AudioLanguages): 1ms SQL3 (Actors): 0ms SQL4 (Directors): 1ms SQL5 (Writers): 1ms SQL6 (Artists): 81ms SQL7 (Genres): 20ms SQL8 (Albumartist): 52ms SQL9 (Composers): 93ms SQL10 (Episode): 1ms SQL11 (DVDEpisode): 1ms SQL12 (Mediaitem): 56ms [U]Restart MP2 Server / Read Test 1:[/U] SQL1 (Genres): 1ms SQL2 (AudioLanguages): 1ms SQL3 (Actors): 1ms SQL4 (Directors): 1ms SQL5 (Writers): 1ms SQL6 (Artists): 80ms SQL7 (Genres): 20ms SQL8 (Albumartist): 53ms SQL9 (Composers): 94ms SQL10 (Episode): 1ms SQL11 (DVDEpisode): 1ms SQL12 (Mediaitem): 55ms As you can see, now the measurements were more or less constant at about 0.3 seconds. The last test I did so far was just doing Read Test 1 again, but this time without restarting the MP2 Server - and again the result was more or less the same: [U] Read Test 1:[/U] SQL1 (Genres): 1ms SQL2 (AudioLanguages): 1ms SQL3 (Actors): 1ms SQL4 (Directors): 1ms SQL5 (Writers): 1ms SQL6 (Artists): 78ms SQL7 (Genres): 20ms SQL8 (Albumartist): 55ms SQL9 (Composers): 93ms SQL10 (Episode): 1ms SQL11 (DVDEpisode): 1ms SQL12 (Mediaitem): 64ms And I already have a suspicion where this comes from - maybe a first hook to implement an optimization. More about it tomorrow... Michael [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Plugin Development
SQLiteDatabase Plugin for MP2
Contact us
RSS
Top
Bottom
