[email protected] wrote:
> 
> 
> Hi,
> 
> I'm following up on my very long thread from back in April/May. Since 
> that time i've removed Zoneminder, so that my mythtv system is just 
> that, nothing else. It's running XFS for the mythtv data. CentOS 5, mythtv 
> 0.21
> 
> And I still get what I refer to as stuttering. I'm watching something 
> through the Haupppage MediaMVP, and the video starts to stutter and 
> then almost locks up, jsut barely staggering forward. The buffers 
> drop down to empty. If I pause, they'll fill back up, but removing 
> pause almost immediately drops them back to 0, and stuttering.
> 
> 
> I still believe the problem is somewhere in the mvpmc code with 
> mythtv. Reasons:
> -I have two mediamvps. If something is being watched via mythtv on 
> both, when stuttering starts on one, it doesn't start no the other.
> -If I let it keep stuttering, it will keep it up as long as I'm 
> willing to tinker with it. Yet if I soft reboot the MediaMVP and go 
> right back to the video in mythtv, I'm good for a while.
> -If I watch something from a cifs share, I don't appear to have the problem.
> 
> Most commonly it starts at about 20 minutes, but not always. I've 
> wondered if it has a correlation to the "Control TCP Receive Buffer" 
> and "Program TCP Receive Buffer" settings, but I've never managed to 
> conclusively notice a difference when changing those settings. What 
> ARE good settings for those two values?
> 
> Any insights?
> 
> Rick
> 
> 
> Rick Steeves
> http://www.sinister.net


How many recordings do you have?

If you have enough, the mvpmc loads all of the data for the recordings 
into memory and if there are too many memory gets tight and it has 
issues.     From my usage the number is 1400-1800 range depending on 
how much data each program has.

Once you get above about 1000 recordings the memory usage is tight 
enough that after watching a few things/a few days things will start 
getting into trouble.

Are you running a fairly new mvpmc?   There was a bug before that 
resulted in a large memory leak, I don't remember how long ago the 
patch for it was committed, but without that patch even with 500 
recordings things would eventually leak enough memory to act like what 
you are describing.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to