Is there anything I can do to make KDE run faster on MD's or is this just a casualty of running diskless MD? I can watch paint peel faster than thinks move in KDE.
Doesn't happen to be an atom is it?
if so sorry .... hazards of an ATOM
HTH
Tim
Zotac zboxes, which I believe are atoms. :(
Why is that? Is there anything I can do to slightly improve this?
To my experience LMCE 8.10 on Atom is slow but still usable, on 10.04 it's snail-speed.
/Joakim
Quote from: JoakimL on December 21, 2011, 06:34:19 PM
To my experience LMCE 8.10 on Atom is slow but still usable, on 10.04 it's snail-speed.
/Joakim
I agree it seems things really got bad in 10.04
Yep I found this also.
Quote from: kyfalcon on December 20, 2011, 05:52:24 PM
Is there anything I can do to make KDE run faster on MD's or is this just a casualty of running diskless MD? I can watch paint peel faster than thinks move in KDE.
Is it the processing that is slow or the video re-render when putting the orbiter on screen? And are you using Alpha blending or overlay? Because those have different requirements and could cause slowdown in different ways with how the cards are accessed and such?
My experience is that LMCE is working great on Atom, it's just KDE that's slow.
/Joakim
my Atom 330/ION seems fine with 0810 as an MD, not sure I have noticed KDE speeds
LMCE works great - KDE snail slow
I am using an Atom MD and for giggles started KDE, when TSCHAK mentioned snail speed. Well, I did not have snail speed, everything worked as expected, as it works on another Atom powered stand alone PC.
According to top, "mythcommflag" is absolutely molesting the resources when I go into KDE desktop, CPU usage does not drop below 99, and often goes above 100, even once the desktop is apparently loaded up. This is 1004. I always found the KDE desktop to be perfectly OK in 810.
This is a known problem, unfortunately, I do not at this time have a solution. Does somebody want to take a crack at this?
-Thom
Thom, are you referring to the slowness issue in general, or specifically to "mythcommflag"? Or is it "mythcommflag" causing the slowness in the first place?
If "mythcommflag" is going mental when you go into KDE desktop, will it also happen when selecting something that opens in a browser from the computing menu? I didn't check this.
It's only for marking adverts/commercials isn't it? Can it safely be killed?
Cheers,
Matt.
No, it's not just mythcommflag, although that could possibly contribute to it. You can turn off mythcommflag in the setup menu of mythfrontend.
-Thom
Ah this explains why I am not seeing this issue. I am one of the few lucky users not needing to run but having the luxury of choosing VDR :P
I disabled commercial flagging in myth frontend, but "mythcommflag" is still chugging away at about 40% with absolutely no media playing. I reset the MD also, and have only been playing music disks since that restart, and it's still there at ~40%.
A few weeks ago I saw some loop in Mythcommflag. The same movie was executed again and again and 10+ processes were running at the same time. I killed them all and restarted the MD; problem solved. After that Mythcommflag is running as it should.
I recall there is a parameter in the MythTV setup where you can control where the Mythcommflag job is executed, though I cannot find it now.
Some googling revieled this that could be worth looking at:
Quote
1) Set max number of jobs to 2. The CPU is dual core and has
hyperthreading enabled, and it handles this without flinching.
2) Enable the ""experimental speedup of commercial detection" option.
With those two settings, I've more than tripled my commercial flagging
throughput.
/Joakim