View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013984 | MMW 5 | Main Panel | public | 2017-02-02 21:19 | 2020-03-01 21:45 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0013984: Prioritize events on MM start | ||||
| Description | MediaMonkey should prioritize what takes place at MM start. Especially on a large database there are several events that can take place at startup and cause DB locks causing others to have to wait. Currently things that may run. 1) Now Playing/Player loading 2) Display of Home and Artwork (needs to be gathered from files if uncached) 3) Podcast downloads 4) Volume Analyzing 5) Video thumbnail creation 6) Online metadata retrieval These processes combined with a large database can cause it to take a couple minutes before MM has loaded all content to the user. MediaMonkey should be as quick as possible be playable (load Now Playing/Player) and then show all content loaded to the user. After that any secondary processes should take place. The secondary processes (3-5) should also be run as lower priority and be broken up into as small as possible SQL chunks so that other processes with higher priority can be expedited. 6 should take place after database data is loaded and displayed. This sequencing is only for database access as this is the bottleneck on a large database. Where possible processes (don't cause long DB locks) can be run parallel. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
This was regression caused by very ineffective SQL added to home view in course of 0013813 i.e. the same fix as for 0013999 (fixed the blocking SQL) But leaving it assigned to me as there is still a room for optimization re the SQLite bottleneck on large DBs. |
|
|
This is also related to 0013897. Some improvements discussed over IM and some of them are already implemented in 2062. |
|
|
Considering this as Resolved for now. |
|
|
Verified 2229 Startup priorities ar OK now, I do not see any non responsive times after main window UI is completely Rendered. |
