View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010229 | MMW v4 | Podcasts | public | 2012-12-14 04:14 | 2012-12-19 02:46 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1 | Fixed in Version | 4.1 | ||
| Summary | 0010229: Slow Podcast updates | ||||
| Description | Based on user logs it looks that MMW checked podcasts one by one instead of multi threading several at once. | ||||
| Additional Information | http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=19393 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1615 | ||||
|
|
Resolved as dup of 0008767 |
|
|
Re-opened, because although 0008767 has been fixed and podcast update was splitted into more threads, it paradoxicaly slowed the process down for some users (ticket XDK-401799). Looking at the log it seems to be SQLite bottleneck. There is a lot of "UPDATE PodcastEpisodes" SQLs and because they are not on the same thread there are some costs involved slowing it down. I don't remember exactly why we updates episode metadata on each podcasts update, but I guess that the reason is that the metadata is getting changed for some podcast feeds. But I guess that we should make this optional, I think adding a checkbox like this: [x] Keep updating episode data by feed data (slower) Hint: 'If episodes data are changed by podcast feed creator, it is updated from the feed' |
|
|
The checkbox added in 1615 Test note: On my machine there is no difference and podcast update takes still the same time, but in my case it is network bottleneck, becuase I have SSD disk and SQL ops are fast. |
|
|
Verified 1615 I do not have SSD but My network down stream is 20Mbits and podcast updates are considerably faster by almost half (11 -> 6 Minutes) |
