Kodi Community Forum

(2013-10-09, 12:11)popcornmix Wrote: [ -> ]I did some work on this yesterday, and it was looking promising. Not quite finished, but should be soon.

Great to hear, thanks

(2013-10-09, 12:54)popcornmix Wrote: [ -> ]@rbej/@MilhouseVH

OpenELEC has changed the default from optimise for speed to optimise for size:
https://github.com/OpenELEC/OpenELEC.tv/...fb9dd1d155

This may (or may not) have a negative effect on the speed of the build. I'd be interested if you can see any difference.

I tested "size" and "speed". No difference in Xbmc performance. Only few MB small build.

(2013-10-09, 12:54)popcornmix Wrote: [ -> ]@rbej/@MilhouseVH

OpenELEC has changed the default from optimise for speed to optimise for size:
https://github.com/OpenELEC/OpenELEC.tv/...fb9dd1d155

This may (or may not) have a negative effect on the speed of the build. I'd be interested if you can see any difference.

Just finished a build from OpenELEC HEAD. Took 5ish hours from pulling new OpenELEC git to finish build on a dual-core Toshiba L500 - [email protected], 4GB RAM, Ubuntu 13.10 x86_64.

Can't really see much of a difference. Did you noticed something?

(2013-10-09, 13:15)hudo Wrote: [ -> ]Can't really see much of a difference. Did you noticed something?

I noticed the commit...

I made a build with the new default (size) and couldn't see a clear difference, but thought it's worth bringing to people's attention.
If it happened to make builds 10% slower, it may not be enough for people to instantly notice, but it would be undesirable.

By mentioning it, someone might report that entering the music view with a large library used to take 30 seconds, and now takes 33 seconds.

Most likely the difference is negligable.

Updated Gotham Branch

- sync with Gotham Popcornmix branch (newclock3)

http://netlir.dk/rbej/builds/

http://lysin.me/rbej

They tend to flip flop on size vs. speed every now and again. It will probably revert at some point in the future...

(2013-10-09, 13:24)popcornmix Wrote: [ -> ]

(2013-10-09, 13:15)hudo Wrote: [ -> ]Can't really see much of a difference. Did you noticed something?

I noticed the commit...

I made a build with the new default (size) and couldn't see a clear difference, but thought it's worth bringing to people's attention.
If it happened to make builds 10% slower, it may not be enough for people to instantly notice, but it would be undesirable.

By mentioning it, someone might report that entering the music view with a large library used to take 30 seconds, and now takes 33 seconds.

Most likely the difference is negligable.

From previous buils I have here, difference in size is ~1MB. I'm building OpenELEC head again optimized for speed just to see the difference.

Should we change to 4 threads in latest build?

(2013-10-09, 14:31)xbs08 Wrote: [ -> ]Should we change to 4 threads in latest build?

Are you talking about bginfoloadermaxthreads on Gotham? Then no, that setting has been removed (it's fixed at 5).

(2013-10-09, 15:06)popcornmix Wrote: [ -> ]Are you talking about bginfoloadermaxthreads on Gotham? Then no, that setting has been removed (it's fixed at 5).

OpenELEC Gotham master still has it set to 2 in the system-wide as.xml, is the setting still being honoured (when present) or ignored completely? I guess the OE developers should remove it if it's no longer used.

I did run some tests with it increased to 4 and thought I saw slightly improved performance (ie. 4 download threads and 4 bginfoloadermaxthreads vs. 4 download threads and 2 bginfoloadermaxthreads) but didn't pursue it.

Not sure if this is the right thread for this, but I recently noticed there is a new PVR addon that supports Windows Media Center as the backend (pvr.wmc). For now they client addon is only supported on raspbmc.

Any thoughts/plans to include the pvr.wmc addon in OpenELEC?

PVR WMC thread link: http://forum.xbmc.org/showthread.php?tid=171216

(2013-10-09, 15:17)MilhouseVH Wrote: [ -> ]OpenELEC Gotham master still has it set to 2 in the system-wide as.xml, is the setting still being honoured (when present) or ignored completely? I guess the OE developers should remove it if it's no longer used.

I did run some tests with it increased to 4 and thought I saw slightly improved performance (ie. 4 download threads and 4 bginfoloadermaxthreads vs. 4 download threads and 2 bginfoloadermaxthreads) but didn't pursue it.

I've grepped the source tree for bginfoloadermaxthreads and it has gone. Disappeared (rather silently) here:
https://github.com/xbmc/xbmc/pull/2890

(2013-10-09, 13:47)rbej Wrote: [ -> ]Updated Gotham Branch

- sync with Gotham Popcornmix branch (newclock3)

http://netlir.dk/rbej/builds/

http://lysin.me/rbej

Is this build faster as the lastest build with Newclock?

(2013-10-09, 16:32)Koloss Wrote: [ -> ]

(2013-10-09, 13:47)rbej Wrote: [ -> ]Updated Gotham Branch

- sync with Gotham Popcornmix branch (newclock3)

http://netlir.dk/rbej/builds/

http://lysin.me/rbej

Is this build faster as the lastest build with Newclock?

Should be.

(2013-10-09, 16:18)popcornmix Wrote: [ -> ]

(2013-10-09, 15:17)MilhouseVH Wrote: [ -> ]OpenELEC Gotham master still has it set to 2 in the system-wide as.xml, is the setting still being honoured (when present) or ignored completely? I guess the OE developers should remove it if it's no longer used.

I did run some tests with it increased to 4 and thought I saw slightly improved performance (ie. 4 download threads and 4 bginfoloadermaxthreads vs. 4 download threads and 2 bginfoloadermaxthreads) but didn't pursue it.

I've grepped the source tree for bginfoloadermaxthreads and it has gone. Disappeared (rather silently) here:
https://github.com/xbmc/xbmc/pull/2890

removed it from as.xml wiki