<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
>> Is anyone else seeing extremely high CPU usage on their backend when<br>
>> playing back *any* content on a remote front end? I just noticed that<br>
>> during playback, the CPU usage of my backend stays around 175-200% on<br>
>> a 2 x Dual core AMD system. I can't imagine what it would be doing<br>
>> other than just streaming the file, is anyone else seeing this, or can<br>
>> explain it?<br>
>><br>
>> I am on close to current master:<br>
>><br>
>> MythTV Version : v0.26-pre-629-g181641a-dirty<br>
>> MythTV Branch : master<br>
>> Network Protocol : 75<br>
>> Library API : 0.26.20120614-1<br>
>> QT Version : 4.6.3<br>
>> Options compiled in:<br>
>> linux profile use_hidesyms using_alsa using_oss using_backend<br>
>> using_bindings_perl using_bindings_python using_bindings_php using_dvb<br>
>> using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv<br>
>> using_ivtv using_joystick_menu using_libcrypto using_libdns_sd<br>
>> using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit<br>
>> using_qtscript using_qtdbus using_v4l2 using_v4l1 using_x11<br>
>> using_xrandr using_bindings_perl using_bindings_python<br>
>> using_bindings_php using_mythtranscode using_opengl<br>
>> using_ffmpeg_threads using_live using_mheg using_libxml2<br>
><br>
> Hmmm....looks like it may have been a memory leak of some sort, I<br>
> started getting OOM killers and lots of swapping. I'll keep an eye on<br>
> it and see if it happens again.<br>
><br>
<br>
</div></div>I love talking to myself. Now with one frontend playing back and two<br>
recordings (1 HDHR and 1 HD-PVR on a slave BE) the BE CPU is over<br>
250%. Lots of free memory (overall system memory is 8GB), so the OOM<br>
doesn't explain it.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div> </div><div>The only things I can think of that MAY cause excessive CPU usage on the backend, explicitly during playback/recording are:</div><div><br>
</div><div>1. Jobs (transcode/commercial flagging)</div><div>2. Degraded software RAID array.</div><div>3. non-DMA disk IO.</div><div>4. Encrypted/compressed drive</div><div>5. non-DMA network controller, or some on chipset NIC and a really horrible network causing a ton of errors?</div>
<div><br></div><div>First try doing a couple of IO intensive tasks to confirm if it's mythtv (perhaps use VLC to stream from the HDHR to a file?). I suspect it's something on the system itself, not mythtv.</div>
<div>
<br></div><div>If I am right I would start by verifying all RAID arrays are clean, and if all looks good, do a full shutdown. Then disconnect power and let it sit for 15 minutes so any charged caps can dissipate before plugging in and turning on. This has fixed countless weird issues for me in the past, primarily with NIC's that support WOL. Seems as though many components of your system don't truly reset anymore until the power is cut completely.</div>
<div><br></div><div>Good luck</div></div>