View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020278 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2023-10-05 03:45 | 2024-03-25 12:42 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1 | Fixed in Version | 5.1 | ||
| Summary | 0020278: Auto-tag: takes much too long (regression) | ||||
| Description | With build 2817 it takes over 20 minutes to auto-tag a set of 87 files! I believe that much of the slowness is related to failed lyric lookups, but am not certain. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2829 | ||||
|
|
I think that the suggested approach of temporarily (i.e. for the duration of the current auto-tag operation) disabling a non-performing server is best. Since this issue is only relevant to auto-tag operations (i.e. mass lookups), and auto-tag operations already indicate status in the Status Bar, perhaps the notification could appear in the status bar? e.g. using existing strings: Source 'xxx': Disabled. p.s. can you indicate how you plan to decide that a server is non-performing? |
|
|
@rusty: I plan to measure typical response time to see how fast/slow the servers normally respond, and during lyrics search will measure time of every request and in case some will be significantly slower (e.g. slower than 2x-3x of "normal" time of the slowest server we use), I will temporarily disable it, because that would mean it's overloaded at the time of this auto-tagging session. Re status bar - could be. |
|
|
Fixed in build 2829. Currently used time limit 9s for disabling server, it seems response duration is mostly 0.2 - 5s, so this could give some reserve, we can adjust it in the future, if needed. I used requested status message, but it is hardly noticeable, as status is immediately overwritten by next status - next server. But I think it is not big problem, as disabling is active only for current autotag session. I tried using toast too, but it is quite irritating in this dialog, so decided to not use it. |
|
|
It works ok for me now in 2829. |
|
|
Re Verified 3007 |
