<div class="gmail_quote">On 4 April 2011 18:42, Niklas Brunlid <span dir="ltr"><<a href="mailto:prefect47@gmail.com">prefect47@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote">On 2 April 2011 20:46, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><div>... <br></div><div><div></div>
<div class="h5"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<br>
To see if you're having data-access problems, try running:<br>
<br>
wget 'http://<masterbackendip>:6544/Myth/GetRecorded' -O /dev/null<br>
<br>
(but change "<masterbackendip>" to the IP address of your master<br>
backend). After, you should see something like (probably about 2x as<br>
large as since I have 1469 recordings):<br>
<br>
100%[======================================>] 1,263,278 --.-K/s in 0.1s<br>
<br>
If so--if you're getting the results in, say, 0.2s or 0.3s--the problem<br>
is likely the mythfrontend sorting/processing of those recordings.<br>
FWIW, with half as many recordings as you have, my system brings up the<br>
Watch Recordings screen in (seemingly a lot less than) 0.5s (I'd guess<br>
0.2 to 0.3s, but can't say for sure). So, either you've surpassed some<br>
performance ceiling, have an underpowered frontend (mine is not an<br>
Atom--it's a real computer--but trying to load that screen with 3K<br>
recordings on an Atom-based system *should* take a long time), or have<br>
some other misconfiguration, such as...<br></blockquote></div></div><div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<br>
Often previews /are/ a problem for users with some MythTV system<br>
misconfigurations--but, as Raymond mentioned, won't be a problem on a<br>
properly-configured system.<br>
<br>
Off the top of my head, reasons I can remember that cause previews to<br>
slow Watch Recordings include:<br>
a) having your (frontend user) $HOME/.mythtv directory on NFS and<br>
disabling file-attribute caching<br>
b) having a broken/not-writable $HOME/.mythtv/{remote,theme}cache<br>
directory<br>
c) having a time difference on your frontend and backend machines<br>
(you should use NTP on all mythtv machines)<br>
<br>
There are probably others, too, but this is a good start of a list of<br>
things to look at.<br>
<br></blockquote><br></div></div>--------------------------------------------------------------------------------------------------------<br>$ time wget 'http://<address>:6544/Myth/GetRecorded' -O /dev/null<br>
--2011-04-04 18:28:38-- http://<address>:6544/Myth/GetRecorded<br>
Connecting to <address>:6544... connected.<br>HTTP request sent, awaiting response... 200 OK<br>Length: 2956015 (2.8M) [text/xml]<br>Saving to: /dev/null<br><br>100%[======================================>] 2,956,015 --.-K/s in 0.01s<br>
<br>2011-04-04 18:28:44 (291 MB/s) - /dev/null<br><br>real 0m5.801s<br>user 0m0.001s<br>sys 0m0.007s<br>--------------------------------------------------------------------------------------------------------<br>
<br>So the actual download goes by quickly, but it takes a few seconds before it starts to receive data.<br><br>System specs: Fedora 13 on an Asus K8V with an AMD64 3000+ and a Sparkle GeForce 9400 GT PCI card, with OpenGL painter and VDPAU output, using DVI->HDMI to a FullHD LCD TV and the SP/DIF of the mainboard directly to the amplifier. The system is somewhat regularly updated against the Fedora and ATrpms repos. MythTV version is release-0-22-fixes 22973.<br>
<br>Everything runs on the same computer, no external file systems, everything on ext3. Recording drives have "rw,data=writeback" flags, used to have noatime and nodiratime but those were removed since I suspected they interfered with thumbnail generation.<br>
<br><br>Is $HOME in (b) above for mythfrontend or mythbackend? The frontend runs as my normal user, the backend runs as root. In the user home remotecache and themecache are writable by user and group, in root:s home I only have themecache and it's writable by root only.<br>
<br>/ Niklas<br><br></div></div></blockquote><div><br>Noted yesterday that the time to enter Watch Recordings is dependant on wether something is currently being recorded... which I guess is related to the theme (ArcLight) flashing "recording" and mythfrontend taking 50-90% or the cpu as long as those entries are visible. The cpu usage goes away if I scroll down or start playback.<br>
<br>/ Niklas<br><br></div></div><br>