No subject

short periods and/or of rather coarse resolution. As can be seen in Nick's
graphs and mine, mythbackend's memory usage can spike alarmingly high at
times, but it generally goes back down to roughly the same level afterwards.
This didn't surprise me at all.

However, there is a shallow but undeniable upward trend in the base level of
VSZ, which does indeed suggest some memory leakage.

It could well be that your limited hardware resources and/or usage pattern
accentuate such leaks to the point where they are more easily observable
over shorter time periods. Certainly one of the difficulties I've had in
analysing the data I was collecting was having the mythbackend process run
for long enough to be meaningful - what with reboots, power outages,
periodic rescanning of multiplexes with mythtv-setup, the two months
continuous uptime is somewhat unsual, and the 75MB growth in VSZ over that
period didn't present a practical usability problem for me.

> You did also use `ps` or similar as the source of the data?

  # cat /etc/cron.hourly/mythbe-memory.sh
  #!/bin/sh
  /bin/echo -n `date` " "  >>/var/log/mythbackend-memory.log \
  ps uawx | grep 'mythbackend' | grep -v grep | head -1 \
  >>/var/log/mythbackend-memory.log

> Please let us know,
> Udo

HTH,
Alex.