Posts: 89
Joined: Apr 2011
Reputation:
0
Greetings,
I have tried out the "dirty regions" function from yesterday's GIT version. It marks the "active" regions fine, but I see absolutely no decrease in CPU usage. On an Asrock A330ION running Linux, the CPU usage is still around 50% in the menu, even when the screen is perfectly still. Is this an expected behavior? Can anyone share their experiences from using "dirty regions" on an ION-powered platform?
Posts: 4,549
Joined: Dec 2007
Reputation:
17
topfs2
Team-Kodi Developer
Posts: 4,549
Dirty regions have been reported to take down CPU usage a bit on some systems. How much depends greatly on the drivers. We minimize what we send to the GPU which means that the CPU will do less work but overall the vast amount of usage decrease is within the GPU and not the CPU.
You might notice more if you set it up to use the nofliptimeout flag.
TBH I must say that 50% in menus sounds almost to much even before D-R, IIRC I have it at around 20% on my ION but it was a long time ago since I had that one up and running.
If you have problems please read
this before posting
Always read the
XBMC online-manual,
FAQ and
search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the
forum rules.
For troubleshooting and bug reporting please make sure you
read this first.
"Well Im gonna download the code and look at it a bit but I'm certainly not a really good C/C++ programer but I'd help as much as I can, I mostly write in C#."
Posts: 1,756
Joined: Feb 2006
have you got update library on strtup and set to run on background?
Posts: 89
Joined: Apr 2011
Reputation:
0
Nope, I always update my library manually.
Posts: 26,215
Joined: Oct 2003
Reputation:
187
nofliptimeout set to 1000 will only do something after nothing is rendered at all for 1 second (i.e. completely static screen for a second).
50% CPU sounds like something is wrong IMO.
Posts: 1,756
Joined: Feb 2006
If you comoile from source,I have noticed this before, you can compile twice the same revision with slight variances, some work better than others.
What I do is compile a second time once i notice something is off. Though this is not always a cure its over 90% cure
for e.g. I activated Dirty regions (1) and noticed when I pull context on any filename half the filename is yellow the rest is white, specially if proceeding the pull context I go to refresh movie information.
I also noticed that though there's no real cpu/gpu usage going marginal latency is introduced, evrything from network is dragging almost a full second.
Another oddity is that any movies in dvd format dont get a little SD flag, removing dirty regions the flag is returned and all of the above goes away.
I haven't noticed any rise on cpu above ~3% unless I'm scrapping then it goes apeshit.
Posts: 1,756
Joined: Feb 2006
with xbmc I try not to assume anything especially on Linux. That recompile thing has fixed a multitude of sins large and small, it was by accident I found this out, when suddenly in one occasion I had what you describe and also just loading up to terminal, terrible picture, and list goes on of things a recompile fixed for me. sometimes I od two in a row as soon the trained eys goes I see something off.
Posts: 1,756
Joined: Feb 2006
thats what I get without dirty regions enabled about 2% on Asrock ION 330 HT using default skin, compiled about 5 minutes ago