Run top in batch mode. It will give you a full , non-curses, output page. You can then copy the header and data lines (trim out the unwanted)
Will running this memory script & logs assist ? Happy to run if it will help.
There seems to be quite a bit of data collected already?
I have also been experiencing this however some things I have noticed:
Server 1
Ubuntu 16.04 running non-docker Plex
Version 1.15.5.994
Regular streams
Regular scans
I have experienced the same memory usage even without a scan running.
Server 2
Ubuntu 18.04.2 LTS running docker Plex
Version 1.16.0.1226
Rare streams, maybe 1-2 every day or two
No scans (no new files added for months)
Something to note: I have tried running my Server 1 Plex on the Server 2 hardware: Ubuntu 18.04.2 LTS with docker Plex and still have high memory usage.
Hopefully this info may be helpful.
I can start gathering logs for Server 1, verbose and debug turned off?
As I have stated: Don’t worry about the Virtual size. Look at the resident size.
PMS is 290 MB resident.
I am looking through what Virt is doing but don’t have anything to give to Engineering yet. It might also be just an artifact of how PMS is written.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
