PMS maintenance activity

General Discussions
1

Hi,

Is there any documentation available that describes what PMS itself does on a regular basis, throughout the day for example? Other than “scheculed tasks” I mean, which I understand (well enough anyway). background of the question is the activity I see in the dashboard, especially the repeatable patterns. I have captured two very interesting “bandwidth” patterns in the attached, where one (more complex) pattern stops and another one takes its place. What is happening here?

2021-12-28 (2)
2021-12-28 (2)1312×381 79.9 KB

Aside from the above, the larger question is this: what PMS activity happens outside of the scheduled tasks timeframe?

Also – I did notice, via Synology task manager, that PMS “Transcoder” appears to wake up every few seconds and consume half of the CPU for a short burst, taking the top spot in the task manager list. Is the transcoder looking for something to do here?

FYI: all of my media is indexed, nothing is playing, I have no transcoced media copies, and all of the scheduled tasks are completed

2021-12-28 (1)
2021-12-28 (1)1601×312 72.5 KB

2

That is the bandwidth used updating the browser page (i.e. the bandwidth graph itself).

Open up another window and look at Settings → Console. You’ll see the associated log entries.

Unable to help with this. I do not see such activity on my Synology.
Maybe a periodic scan (Settings → Library)?

3

I turned off “webhooks” and “enable relay” and now the network activity looks like this:

2021-12-28 (2)
2021-12-28 (2)1312×381 79.6 KB

and after making this change I also noticed that the transcoder doesn’t fire up anymore. I wonder if this is about the relay itself requiring the transcoder to reduce things down to the bandwidth allowed by the relay, which I think is 2Mbps . that would make sense – the transcoder was probably looking for something to do.

But the above pattern is very interesting…

4

There’s a fairly simple test you can perform if you’d like to confirm for yourself that it is indeed the web client’s connection to the server itself which is causing the pattern you see above: Close the web page for 45-60 seconds and then reopen it and view the Dashboard. You should notice a corresponding gap in the bandwidth chart. That’s not because it’s not being measured when the page isn’t loaded; it is measured at all times. It’s because that bandwidth is no longer being used to update the page.

5

yea the web client makes sense. the gradually-increasing baseline is curious but indeed I can see that you guys are right on that point. It also appears that the transcoder does wake up at some periodicity to see if there is relay work to do