View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016128 | MMW 5 | Sync | public | 2019-11-21 12:02 | 2020-10-11 21:10 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0016128: Initial cloud service scanning is much slower than used to be | ||||
| Description | As reported here: https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=95432 50K of tracks were scanned from Google Play Music to the MM5 library in 6:39 With recent builds it takes 1:45:15 ! Debug logs sent via PM | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2214 | ||||
|
|
I cannot replicate the issue (in my case 10K of tracks were scanned in 3 minutes). But from the Barry's debug log I can see that track notifications are slow in his environment, debugging further via PMs... |
|
|
Test note: It seems that the key to reproduce is to have all library tracks loaded in the Playing panel i.e. the performance is degraded with amount of tracks added to Now Playing. Fixed in 2214 |
|
|
GPM is not available anymore. No regression or scan slowdowns are found during test of other cloud services (eg. dropbox, Google drive, one drive) |
