MediaServer web interface slow

[reki]

I have following setup:

 

• Windows 10.
• MediaServer 3.3.1.0.
• Local Digital Devices Max S8 tuner to record DVB-S streams.
• Several TS Stream Device recording Internet radio.
• At any given time, about 40 timers programmed, simultaneously recording ~10 channels: DVB-S and Internet.

 

The interface is sluggish, clicking on any tab (Timeline, Timers, Status, Configuration) takes >= 10 seconds to load. Sometimes freezes are much longer. Recordings seem to be unaffected, we see they come in time. The CPU stays at ~2.5% and memory usage at 180 MB. I don't see memory increase.

 

The issue seems to be similar to my previous issue: https://www.DVBViewer.tv/forum/topic/74183-mediaserver-web-interface-extremely-sluggish/  but I tried deleting SvcDatabase.db3 and no change. Also, no elevated CPU and memory usage.

 

support.zip

[Griga]

vor 9 Stunden schrieb reki:

Several TS Stream Device recording Internet radio (...) The interface is sluggish, clicking on any tab (Timeline, Timers, Status, Configuration) takes >= 10 seconds to load.

 

It is most likely caused by repeated attempts to record one or more non-working internet radio channels. There are a lot of "SetTuner failed" entries in your svcdebug.log. Probably the radio server does not reply, for whatever reason, so the tuning procedure waits until the connection timeout has elapsed (default 5000 milliseconds, see settings of your TS Stream devices). During this time the Media Server is not able to respond to other requests. It becomes a permanent issue, because the recorder tries again and again to start a recording of this channel, until the timer end time is reached.

 

There are two measures that have to be taken. One is up to you, the other one up to me:

• You need to clean up your timer list and make sure that it only contains timers for radio channels that are working reliably.
• I have to think about measures that avoid such uselessly repeated recording attempts, e.g. by letting the recorder give up after a certain number of failed attempts, or retry tuning only once per minute.

I will let you know as soon as I have a solution for it...

 

[Griga]

Now I have some time to look after this, but I'm a bit unsure how to handle it. Basically there are four possibilities:

1. Drop the recording, if tuning fails, without further attempts to start it. This could cause a temporary delay in the web interface, but  only once per timer.
2. Drop the recording after a limited number of x tuning attempts, hoping that the channel will become available within x seconds. This could cause a longer temporary delay in the web interface, but  only once per timer.
3. Retry to start the recording once per minute (or some other interval), hoping that the channel will become available again sooner or later. However, this could still make the web interface sluggish every now and then, particularly if tuning fails for more than one timer.
4. A combination of 2. and 3, hoping that the channel will become available within x minutes.

Am 12.1.2026 um 19:42 schrieb reki:

At any given time, about 40 timers programmed, simultaneously recording ~10 channels: DVB-S and Internet.

 

What would you prefer from your experience as as "power recorder"?