2025-05-09, 10:26 PM
Digging into the plugin's code, did I get this right, "MediaBrowser" is a shared service from the Jellyfin main application offering access to media lists?
I'm asking as from what i experience, listing of media is terribly slow in the DLNA plugin, so I'm trying to find the root cause. The plugin itself doesn't seem to do a lot regarding listing, it seems to be more or less consuming data from the Jellyfin's datamodel represented by the "MediaBrowser". Did i get this right?
This also means, the plugin itself is not holding/managing an index. Does "MediaBrowser" use a media file cache/index? I can see Jellyfin consumiung a fair amount of RAM even when idle, so my thoughts are, that this cache/index could be hold in memory? I'm asking the listing from then DLNA plugin is so slow that not caching/keeping the file list in memory could be an explenation.
Other than this: Did I get it right that the DLNA device's profile doesn't have an effect in performance and how lists are handled? That's a least the impression I get from reading the profile's xml files.
I'm asking as from what i experience, listing of media is terribly slow in the DLNA plugin, so I'm trying to find the root cause. The plugin itself doesn't seem to do a lot regarding listing, it seems to be more or less consuming data from the Jellyfin's datamodel represented by the "MediaBrowser". Did i get this right?
This also means, the plugin itself is not holding/managing an index. Does "MediaBrowser" use a media file cache/index? I can see Jellyfin consumiung a fair amount of RAM even when idle, so my thoughts are, that this cache/index could be hold in memory? I'm asking the listing from then DLNA plugin is so slow that not caching/keeping the file list in memory could be an explenation.
Other than this: Did I get it right that the DLNA device's profile doesn't have an effect in performance and how lists are handled? That's a least the impression I get from reading the profile's xml files.