LinHES Forums
http://forum.linhes.org/

GUI frontend
http://forum.linhes.org/viewtopic.php?f=11&t=15626		 Page 1 of 1
Author:  donjski [ Sat Jun 16, 2007 1:32 am ]
Post subject:  GUI frontend
Certain parts of the gui are slow. It seems as though I didn't hit the button on the remote sometimes.

I am running R5F1 with a Geforce FX 5700 LE 128mb card

I have recently upgraded from R5D1 with which I only had a 32 mb nvidia card and never saw these problems.

I have checked the bios settings to make sure I am running my new card at the right speed, but i still have the hangs between some screens in the GUI.

Could something else be causing this?

cheers
Author:  tjc [ Sat Jun 16, 2007 8:13 am ]
Post subject: 
The known button losses with the remotes?

See the R5F1 hints for the link to a thread with two possible solutions to try.
Author:  donjski [ Sat Jun 16, 2007 10:47 am ]
Post subject: 
No, it's not a remote problem. I just said that it seemed that way to explain what I am experiencing. I get the same pauses usiing the keyboard too.
Author:  slowtolearn [ Sat Jun 16, 2007 11:53 am ]
Post subject: 
donjski wrote:
No, it's not a remote problem. I just said that it seemed that way to explain what I am experiencing. I get the same pauses usiing the keyboard too.
What are your system specs?
Author:  donjski [ Sat Jun 16, 2007 12:57 pm ]
Post subject: 
512 mb ram
AMD 1600+
128 MB Nvidia Geforce 5700 FX LE
Seagate IDE harddrives all 7200 speed
Hauppage PVR-150 w\ dogbone remote
Asus Motherboard w\ integrated surround audio I think it a K7M, not sure, I would have to open the box to check for sure.


need more?

thanks
Author:  slowtolearn [ Sun Jun 17, 2007 7:33 am ]
Post subject: 
donjski wrote:
512 mb ram
AMD 1600+
128 MB Nvidia Geforce 5700 FX LE
Seagate IDE harddrives all 7200 speed
Hauppage PVR-150 w\ dogbone remote
Asus Motherboard w\ integrated surround audio I think it a K7M, not sure, I would have to open the box to check for sure.
If this box is a combined backend/frontend and you are commflagging or transcoding you could see that type of reaction. Does top show high CPU-usage when you experience this? Are there any errors in /var/log/syslog, /var/log/messages or /var/log/mythtv/mythbackend.log?
Author:  donjski [ Mon Jun 18, 2007 6:43 pm ]
Post subject: 
Quote:
If this box is a combined backend/frontend and you are commflagging or transcoding you could see that type of reaction


It is not used for this.

But I did run top and it does show extremely high CPU usage for 'mythfrontend' on the slow loading pages.
Author:  tjc [ Mon Jun 18, 2007 8:36 pm ]
Post subject: 
What are your appearance settings? Especially your GUI rendering techniques? Some of the new ones can be pretty CPU intensive...
Author:  slowtolearn [ Mon Jun 18, 2007 8:39 pm ]
Post subject: 
donjski wrote:
Quote:
If this box is a combined backend/frontend and you are commflagging or transcoding you could see that type of reaction


It is not used for this.
Not used for what? The combined frontend/backend, transcoding and/or commflagging, all of the above? The more information you supply the higher the likelyhood that someone will be able to help you.

donjski wrote:
But I did run top and it does show extremely high CPU usage for 'mythfrontend' on the slow loading pages.
Could you post some of the output? Also run vmstat 3 and post some of that output.

Also, which theme are you using?
Author:  donjski [ Mon Jun 18, 2007 11:17 pm ]
Post subject: 
It's not used for commflagging or transcoding. I don't use it for the tv part.

I am using the NEON theme, but I see the same lag with all themes, Even more with blootube. Some times i have to restart X for blootube.

Here is vmstat 3:



Code:
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa
 0  0 421120  16336   3048 136636   10   13    51   141   44   82 21  2 76  1
 2  0 421076  16064   3056 137248   11    0    11    11 1120  927 28  4 67  0
 2  0 418672  13276   3056 136696  921    0   937     0 1189 1443 80 11  0  9
 0  0 418672  13276   3064 136684    0    0     0    19 1124 1211  2  2 96  0
 0  0 418672  13300   3072 136684    0    0     0     4 1117  648  0  1 99  0
 0  0 418672  13292   3072 136684    0    0     0     0 1132 1259  4  2 94  0
 2  0 418660  13152   3080 137220    3    0     3    37 1133 1347 72 10 17  0
 0  0 418124  12532   3080 136700  232    0   232     0 1133 1477 39  7 51  3
 0  0 418124  12548   3088 136684    0    0     0    11 1132 1344  4  3 93  0
 2  0 418108  12408   3096 137240    4    0     4    17 1123 1384 45  8 47  0
 0  0 417520  11912   3096 136684  211    0   211     0 1143 1476 66  9 23  2
 0  0 417520  11912   3104 136684    0    0     0    23 1115 1005  1  2 97  0
 0  0 417496  11928   3104 136704    1    0     1     0 1148 1516  4  3 93  0


Notice, the large bo's (whatever they are) are during a page lag.


TOP:

The large cpu usage was a snapshot during a page lag.

Code:
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND           
16340 mythtv    25   0  434m  92m 7604 R 44.9 18.4 332:07.10 mythfrontend       
16296 root       0   0  339m 195m 3652 S  5.7 39.0 114:21.35 Xorg               
 2828 root       0   0     0    0    0 R  0.7  0.0  16:14.90 lirc_pvr150       
 9398 root       0   0  2328 1160  880 R  0.7  0.2   0:00.21 top               
    1 root       0   0  2036  308  284 S  0.0  0.1   0:00.96 init               
    2 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0       
    3 root       0  19     0    0    0 S  0.0  0.0   0:00.18 ksoftirqd/0       
    4 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 watchdog/0         
    5 root       0  -5     0    0    0 S  0.0  0.0   0:01.22 events/0           
    6 root       0  -5     0    0    0 S  0.0  0.0   0:00.00 khelper           
    7 root       0  -5     0    0    0 S  0.0  0.0   0:00.00 kthread           
   10 root       0  -5     0    0    0 S  0.0  0.0   0:00.41 kblockd/0         
   11 root      13  -5     0    0    0 S  0.0  0.0   0:00.00 kacpid             
  127 root      10  -5     0    0    0 S  0.0  0.0   0:00.00 kseriod           
  242 root       0   0     0    0    0 S  0.0  0.0   0:46.42 kswapd0           
  243 root      39  19     0    0    0 S  0.0  0.0   0:00.71 kprefetchd         
  244 root      13  -5     0    0    0 S  0.0  0.0   0:00.00 aio/0         


FYI. I never had this issue in r5d1, plus I had a significantly inferior video card then too...only 32mb card.

But i did not have wide screen then.

The only reason I am posting this is for the fact that it is the most notable difference in usability that I have seen.

BTW, not a remote problem...
Author:  donjski [ Wed Jun 20, 2007 10:32 pm ]
Post subject: 
After a little more playing around with this I have found that the menu choice makes a big difference

Right now the slow page loads happen in 'classic' mode. If I change it to 'Default' things speed up quite a bit. This is all using the Neon theme.

Now if I use the original MythCenter theme, I get the same effects, but it is not as slow. Then I tried the MythCenter-wide, it was slow, but not as slow as Neon and not as fast as the Myth-wide version.

So, does anyone else see this happening? Try classic under 'menu theme' in Setup\Appearance.

I am using the default paint engine QT. I tried OpenGL with the same effects...
Author:  mogator88 [ Thu Jun 21, 2007 9:28 am ]
Post subject: 
Yeah I've noticed my menus moving slowly too. I just figured it was normal. I'll watch this thread and try some changes over the next few weeks and report back. Using R5E50.
Author:  deontaljard [ Tue Jul 10, 2007 4:28 am ]
Post subject: 
I've been out of the Knoppmyth scene for a while - no time :D

I installed R5F1 on a epia m12000 and previous versions ran really well on this board. With R5F1 I noticed the symptoms described in this thread as well - haven't checked cpu load etc.

Anyway I googled a bit and found this : http://threebit.net/mail-archive/mythtv ... 51604.html

I haven't checked at home yet but will do so tonight to see if it's related.

Edit: Turns out it wasn't the problem in the thread - interesting read though.

Seems to be gone now - might have been a background job - will keep an eye on it
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/