Reply to thread

Message

<blockquote data-quote="mbuzina" data-source="post: 654563" data-attributes="member: 12382">Re: AW: Re: MP2, plugins, and multiple clients.I would say: combine the caches. * Server RAM Cache: cache the most frequently used thumbs. Use a fixed size buffer that can be changed in settings or allow a buffer to use a dedicated portion of the available RAM. Test if this gives speed improvements.* Client HDD: Yes, you would need that. TV Channel Icons / Thumbs, Album thumbs &amp; Picture thumbs could be cached in seperate caches (so that browsing a huge picture library does not throw out the more regularly used Album thumbs or TV Channel). So have a cache for each group and do a LRU algorithm on that. Check Updates in intervals (thumbs do not update often). Fan Art for me would be optional, I don't mind waiting a 1nd for the one image, but I mind waiting 0.01 second per thumb if I am browsing &gt;1000 items (= 10 seconds!).* Client Memory: Yes, for some this might also help. Probably cache the thumbs of the current &quot;module&quot; / &quot;view&quot; / &quot;window&quot; or &quot;Plugin&quot; (or whatever). You would probably go forward, backward a few times, so caching them in memory speeds up as well.Also allow the caching to be &quot;invisible&quot;. If you have an interface called the &quot;[CODE]ThumbsProvider[/CODE]&quot; (method would be [CODE]tp.GetThumb(mediaItem);[/CODE]or [CODE]tp.GetThumbs(mediaItemList);[/CODE]) you could create a class called [CODE]localRAMCacheThumbsProvider[/CODE] (which takes a normal ThumbsProvider in its constructor) and a class called [CODE]localHDDCacheThumbsProvider[/CODE] (which also has such a constructor), you could call:[CODE]tp = new localRAMCacheThumbsProvider(new localHDDCacheThumbsProvider(new fromServerThumbsProvider))); [/CODE]if you wanted all caches or leave one out.Just my 2 cents.</blockquote>

[QUOTE="mbuzina, post: 654563, member: 12382"] [b]Re: AW: Re: MP2, plugins, and multiple clients.[/b] I would say: combine the caches. * Server RAM Cache: cache the most frequently used thumbs. Use a fixed size buffer that can be changed in settings or allow a buffer to use a dedicated portion of the available RAM. Test if this gives speed improvements. * Client HDD: Yes, you would need that. TV Channel Icons / Thumbs, Album thumbs & Picture thumbs could be cached in seperate caches (so that browsing a huge picture library does not throw out the more regularly used Album thumbs or TV Channel). So have a cache for each group and do a LRU algorithm on that. Check Updates in intervals (thumbs do not update often). Fan Art for me would be optional, I don't mind waiting a 1nd for the one image, but I mind waiting 0.01 second per thumb if I am browsing >1000 items (= 10 seconds!). * Client Memory: Yes, for some this might also help. Probably cache the thumbs of the current "module" / "view" / "window" or "Plugin" (or whatever). You would probably go forward, backward a few times, so caching them in memory speeds up as well. Also allow the caching to be "invisible". If you have an interface called the "[CODE]ThumbsProvider[/CODE]" (method would be [CODE]tp.GetThumb(mediaItem);[/CODE]or [CODE]tp.GetThumbs(mediaItemList);[/CODE]) you could create a class called [CODE]localRAMCacheThumbsProvider[/CODE] (which takes a normal ThumbsProvider in its constructor) and a class called [CODE]localHDDCacheThumbsProvider[/CODE] (which also has such a constructor), you could call: [CODE]tp = new localRAMCacheThumbsProvider(new localHDDCacheThumbsProvider(new fromServerThumbsProvider))); [/CODE] if you wanted all caches or leave one out. Just my 2 cents. [/QUOTE]

Verification