mythfrontend runs choppily due to background processes

Bug #191165 reported by pigah
2
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: mythtv

Since the update to .21 in Hardy, whenever anything else is being run on my combined backend/frontend, playback is choppy. This means that transcoding or mythfilldatabase runs that are scheduled by the backend make playback unbearable.

Related branches

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mythtv - 0.21.0~fixes15967-0ubuntu2

---------------
mythtv (0.21.0~fixes15967-0ubuntu2) hardy; urgency=low

  * Replace --tune=i686 and --cpu=i686 as it was a performance loss
    to tune to generic. (LP: #191165)
  * Build with unadvertised faad support.
  * Build with unadvertised faac support.
  * Build with unadvertised libmp3lame support.
  * Build with unadvertised liba52 support.
  * Build with unadvertised libx264 support.
  * Build with unadvertised libxvid support.

 -- Mario Limonciello <email address hidden> Sat, 16 Feb 2008 02:07:39 -0600

Changed in mythtv:
status: New → Fix Released
Revision history for this message
pigah (jumbanho) wrote :

I'd like to reopen this bug on mythtv-0.21.0~fixes15967-0ubuntu2

Revision history for this message
laga (laga) wrote :

Ok, I'm reopening because you still seem to have problems.

I just don't know what's causing them :)

Did your problems show up when you upgraded your box to hardy or when you upgraded MythTV to 0.21?

Are processes like mythcommflag still reniced as they should be?

Changed in mythtv:
status: Fix Released → New
Revision history for this message
laga (laga) wrote :

Can you please the output of "vmstat 2" while you're having problems? Let vmstat run for a minute or so, that should be enough.

Revision history for this message
pigah (jumbanho) wrote : Re: [Bug 191165] Re: mythfrontend runs choppily due to background processes

On Tuesday 19 February 2008 08:05:14 am laga wrote:
> Can you please the output of "vmstat 2" while you're having problems?
> Let vmstat run for a minute or so, that should be enough.

see attached.

procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r b swpd free buff cache si so bi bo in cs us sy id wa
 1 0 22604 5980 9508 255788 0 0 38 115 484 8 10 3 87 1
 1 0 22604 6728 9276 255664 0 0 194 246 525 776 97 3 0 0
 2 0 22604 6300 9288 254240 0 0 130 408 7077 14105 93 7 0 0
 4 0 22604 6264 8920 253992 0 0 202 774 5231 10143 87 13 0 0
 4 1 22604 5664 8592 251596 0 0 64 722 5460 10348 93 7 0 0
 3 0 22604 8192 8564 248352 0 0 70 476 1290 2226 79 22 0 0
 6 0 22604 11252 8600 245580 0 0 64 790 1312 2297 78 23 0 0
 3 0 22604 15584 8628 241432 0 0 64 840 1326 2248 82 18 0 0
 5 0 22604 18704 8656 238436 0 0 66 804 1316 2337 80 20 0 0
 3 0 22604 17356 8688 239916 0 0 64 816 1314 2306 80 20 0 0
 2 0 22604 15744 8712 241428 0 0 64 740 1287 2172 81 19 0 0
 3 0 22604 14276 8736 242920 0 0 64 738 1327 2334 81 20 0 0
 2 0 22604 12792 8768 244452 0 0 64 794 1302 2287 79 21 0 0
 4 0 22604 11308 8792 245912 0 0 66 722 1359 2419 77 23 0 0
 4 0 22604 9252 8812 247412 0 0 64 804 1331 2403 79 22 0 0
 3 0 22604 8028 9088 248860 0 0 64 1544 1452 2460 76 24 0 0
 4 0 22604 6432 9112 250328 0 0 66 760 1322 2302 78 22 0 0
 3 0 22604 5824 9104 250772 0 0 64 782 1363 2419 81 19 0 0
 3 0 22604 6380 9072 250456 0 0 128 798 1316 2302 77 23 0 0
 2 0 22604 5788 9072 250920 0 0 64 914 1376 2367 79 22 0 0
 4 0 22604 5504 9068 251224 0 0 64 736 1326 2412 81 20 0 0
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r b swpd free buff cache si so bi bo in cs us sy id wa
 3 0 22604 5996 9036 250808 0 0 64 388 1330 2356 79 21 0 0
 3 0 22604 6520 8992 250156 0 0 64 774 1353 2407 80 20 0 0
 3 0 22604 5968 9000 250876 0 0 64 774 1316 2397 80 20 0 0
 2 0 22604 6376 8888 250384 0 0 64 718 1305 2286 79 21 0 0
 5 0 22604 5824 8908 251148 0 0 64 730 1360 2443 76 24 0 0
 3 0 22604 5552 8904 251376 0 0 66 724 1334 2422 78 22 0 0
 4 0 22604 5976 8620 251068 0 0 64 782 1331 2349 76 24 0 0
 2 0 22604 5636 8620 251560 0 0 64 724 1355 2384 79 22 0 0
 5 0 22604 5952 8588 251148 0 0 64 774 1345 2447 75 26 0 0
 6 0 22604 5604 8584 251636 0 0 64 720 1328 2343 79 21 0 0
 2 0 22604 6156 8552 251004 0 0 64 734 1314 2327 80 20 0 0
 4 0 22604 6244 8540 250860 0 0 130 822 1345 2419 80 20 0 0
 3 0 22604 5896 8532 251256 0 0 0 732 1339 2381 79 21 0 0

Revision history for this message
pigah (jumbanho) wrote :

On Tuesday 19 February 2008 08:04:00 am laga wrote:
> Ok, I'm reopening because you still seem to have problems.
>
Thanks!
> I just don't know what's causing them :)
>
> Did your problems show up when you upgraded your box to hardy or when
> you upgraded MythTV> to 0.21?
>
Upgraded to .21 (.20.99 to be precise)
> Are processes like mythcommflag still reniced as they should be?
>
Yes reniced to 18
> ** Changed in: mythtv (Ubuntu)
> Status: Fix Released => New

Revision history for this message
pigah (jumbanho) wrote :

The most recent upload (0.21.0~fixes16259-0ubuntu1) seems to have fixed this issue. I notice that the cpu load of mythfrontend is down by about 1/2.

Thanks!

Changed in mythtv:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.