[mythtv] Profiling myth

[James Courtier-Dutton]

On 3 June 2010 20:35, Martin Ritchie <ritchiem at apache.org> wrote:
>
> From the sounds of things there are a lot of items that have been
> 'tuned' to the general case just now. Whilst the performance I have is
> acceptable it would be neat if there was a configuration page where
> these defaults could be adjusted. That way if someone has a really
> slow firewire device they could provide specific feedback to improve
> that device. The docs per device (or at least the devices I've used)
> are excellent including a number of tweeks to get the best from the
> setup.
>
> If the only output from your endevour is to expose these tuning values
> to allow the comunity to be better able to tune their installs I said
> that is a win.
>
> Martin
>

I have only just started looking at the code base for myth.
It is large.
Fortunately, when I ask questions on this list, I seem to be getting
good answers, so I will hopefully be up to speed on the code soon.
So far, for my DVB setup.
I get myth doing about 2 seconds between tune request and first TS packet.
I then get 6 seconds before the first new frame displayed on the frontend.
So, currently I have an 8 second channel change time.
I agree with you, adding config items so users can "tune" their own
setups is a good idea.

Currently, I am having a little trouble tracking down all the
different ring buffers, and where they get instantiated and deleted.
Once I understand the flow of the ts packets through the code, I will
be able to make a proper start on the profiling.
If anyone can point me to a wiki page explaining it, It would be a great help.