Remote performance issues compared to web access

Server Version#: 1.20.0.3133
Player Version#: 3.1.1 / 4.34.4

I’m accessing my Synology NAS-hosted Plex music library remotely, via PlexAmp on MacOS. It takes noticeably longer to load the list of albums (title, disc image) and start playback via PlexAmp than via the web interface. Are there any settings I should be looking at tweaking or could this be a bug in PlexAmp/server communication?

@elan Just in case you missed this re #plexamp

Hmm, that shouldn’t be the case. I can’t think of any reason why that would happen :thinking:

I’m motivated to dig into this :wink:

The locations where slowness is easily observed:

  • “Second tab” in PlexAmp takes 10-20 seconds to load artist/album/etc counts for ~500 artists, ~1200 albums and ~13000 tracks. The web UI switches instantaneously between artist/album views with the counters immediately correct.
  • Opening “albums” in PlexAmp and scrolling to the bottom takes “a little while” to load the titles, a “long while” to load the codec/bitrate and I got this far in typing this post still waiting for the ~8 visible cover images to load. The web UI doesn’t show codec/bitrate but the rest is basically instantaneous with ~20 covers visible.
  • Playback starts in about the same time, although even with playback running the PlexAmp cover image doesn’t load.
  • All of these are reproducible across PlexAmp restarts so - there’s no local cache?

I’m happy to collect logs if you point me the right way.

I am also having performance issues with plexamp. In particular large playlists. I have a playlist with 507 items on it, if I press shuffle it will never play unless I am local and connected to wifi. If I select any one particular song on the playlist, the song begins to play as normal.

I’d recommend optimizing your database to start (and make sure this succeeds). That tab loads for me in a second or two with 64k tracks.

All of those other things also point to poor server/db performance, which might be related to an unoptimized database or else a really really slow machine w/spinning disk?

For good measure I optimized the DB but it didn’t make much of a difference.

Indeed the server side is on a spinning disk on a Synology DS218+ NAS but I don’t expect that should be a bottleneck, especially since the exact same music library works very well on the web client as well as Android PlexAmp, using all the same networks.

Maybe there is some excessive network chatter that is only present with the MacOS client and doesn’t work well over my 3000 miles client-server distance?

i mean, there’s a number of requests occurring to fill in that library screen (figure one request per count shown there).

opening an album has a few requests, but nothing crazy. the codec/bitrate adds another request per album.

i’d be curious to see you: a) load up the libraries screen b) send me your media server logs right after so i can see how long the requests are taking.

I sent logs for connections from both the MacOS and Android PlexAmp clients in a PM.

(replied in the PM)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.