I can stream/watch 4 SD unencrypted streams at the same time, each from a different muxes for an hour without a problem. Haven't tested for a longer time period.
When I start recording more than 1 stream, to a windows share (so not through USB), stream profile "pass", cache scheme "don't keep", both network traffic nor processor are a problem. But available memory goes down and when it's too low, the process is stopped, processor spikes.
After the above, I stopped watching the 4 streams, started recording 2 streams. Than stopped 1 of them, so I'm recording just 1 stream.
Resident memory still goes up, now abount 308MB, virtual memory about 725MB. TvHeadend gui becomes unresponsive, I can't reach it anymore. Have to stop the service after which memory goes up.
Restarted service tvheadend, which continues to record the 1 stream. Free memory goes down to about 25MB, available memory stays at about 733MB. Then 18 minutes after the start of the recording, maybe at that time I tried adding a recording after the one I'm recording at the moment, Kodi gives me a pvr error and I can't program a new show. Than free memory goes up and available memory goes down. These last both continue to go down. TVHeadend gui becomes unresponsive, I can't reach it anymore. Have to stop the service after which memory goes up.
14:40 Restarted service tvheadend, which now doesn't go further recording the old show. Started recording 1 new show. Available memory looks stable at 734MB, free memory going down starting at about 617MB. Now I'm not touching pi/tvheadend/kodi again.
14:41 free memory goes down again
14:46 free memory goes up, then down again and now available memory also goes down which is usually the sign of the start of a bad thing.
15:15 memory seems to be stabilizing at: available 518MB, free 379MB.
16:00 free memory stable at 25MB, available down to 80MB. TVHeadend gui becomes unresponsive, I can't reach it anymore. Have to stop the service after which memory goes up.
16:05 +Now changing configuration to store recordings locally (in pi) instead of on windows share+. Keeping stream profile "pass", cache scheme "don't keep". Recording 1 show.
16:24 Free memory went down immediately to a stable 26MB, available seems stable at 728 MB.
16:49 Stable.
17:22 Stable. Added a second recording (different mux). Free 666MB, available 759MB.
18:02 Stable.
18:11 Stable. Added a third recording (different mux). TVHeadend gui unresponsive, I can't reach it anymore.
When I type: sudo service tvheadend status -l, I get:
Loaded: loaded (/etc/init.d/tvheadend)
Active: active (exited) since zo 2017-02-19 16:02:13 CET; 2h 18min ago
Process: 26325 ExecStop=/etc/init.d/tvheadend stop (code=exited, status=0/SUCCESS)
Process: 26408 ExecStart=/etc/init.d/tvheadend start (code=exited, status=0/SUCCESS)
feb 19 18:00:53 raspberrypi tvheadend[26419]: mpegts: too much queued table input data (over 2MB), discarding new
Syslog:
Feb 19 18:00:10 raspberrypi tvheadend[26419]: mpegts: too much queued table input data (over 2MB), discarding new
Feb 19 18:00:13 raspberrypi tvheadend[26419]: mpegts: too much queued table input data (over 2MB), discarding new
Feb 19 18:00:13 raspberrypi tvheadend[26419]: mpegts: too much queued table input data (over 2MB), discarding new
Feb 19 18:00:13 raspberrypi tvheadend[26419]: mpegts: too much queued table input data (over 2MB), discarding new
Feb 19 18:00:14 raspberrypi kernel: [118212.710689] TCP: request_sock_TCP: Possible SYN flooding on port 9982. Sending cookies. Check SNMP counters.
Feb 19 18:00:16 raspberrypi tvheadend[26419]: htsp: 192.168.2.1 [ tvheadend | Kodi Media Center ]: Write error -- Gebroken pijp
Feb 19 18:00:20 raspberrypi tvheadend[26419]: mpegts: too much queued table input data (over 2MB), discarding new
Stopping tvheadend service.
I think I've got another problem here (broken pipe). Any help appreciated.
Wim