Video of latest xbmc code on Raspberry Pi
(2013-09-30, 22:42)popcornmix Wrote:
(2013-09-30, 20:24)MilhouseVH Wrote: Many thanks for the details explanation. Would destroying textures more frequently be of any benefit, say 2-3 seconds rather than 5? Perhaps keep 5 seconds for 720 (or less), and use a lower (faster) value for >720, unless there's a performance downside of course.

Yes, when tracking down the texture leak bug ( I set the timeout to zero, and didn't see much change.
Change the 5000 to 0 (or something else) is you want to test it:

I guess it only helps when you backtrack. i.e. scroll too far and then go back (although one row off each end of screen is cached anyway).

Thanks. I'll re-cache my fanart at 1080 and see if 5 seconds is a problem (over NFS, still waiting for the USB3 memory stick). I'll then use a delay of 0 and see if I notice any difference. One thing that occurs to me is that, if GPU memory is limited, couldn't textures simply be evicted from GPU RAM as required? Then you could have a longer lazy eviction time, but also evict on demand if/when required to free up RAM.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.

Messages In This Thread
RE: Video of latest xbmc code on Raspberry Pi - by Milhouse - 2013-10-01, 00:04
RE: - by godson - 2013-10-13, 00:29
USB 2.0 vs. Class 10 vs. USB 3.0 - by xbs08 - 2013-12-13, 11:56

Logout Mark Read Team Forum Stats Members Help
Video of latest xbmc code on Raspberry Pi6
This forum uses Lukasz Tkacz MyBB addons.