Comments on: Caching images loaded from a spark item renderer

By: Francisc

Francisc — Sun, 05 Sep 2010 08:38:09 +0000

Excellent article, thank you.

By: Andre

Andre — Mon, 26 Jul 2010 20:09:46 +0000

Thanks for this info! For my application I actually needed the useVirtualLayout option, but it was good to see the different approaches. I would be interested in seeing your implementation of the common cache algorithms.

By: Bjorn

Bjorn — Mon, 18 Jan 2010 22:26:22 +0000

That cache algorithms link is gold! thanks Steve.

By: Steven Shongrunden

Steven Shongrunden — Mon, 18 Jan 2010 18:24:36 +0000

@TK – Thanks for the feedback

By: TK

TK — Mon, 18 Jan 2010 17:13:16 +0000

Very helpful. A great post, definitely bookmarking this. Thanks!

By: Steven Shongrunden

Steven Shongrunden — Mon, 18 Jan 2010 07:34:16 +0000

@Bjorn – Deciding when to remove an item from a cache is a common problem and there are some commonly used strategies, for example:

1. Keep track of how often an item has come into view and only remove items from the cache that aren’t viewed very often (Least Frequently Used)
2. Keep track of the time an item was last in view and…
– remove the item that hasn’t been viewed for a while (Least Recently Used)
– remove the item that is currently in view (Most Recently Used)

In this case deciding which approach to take will likely depend on your data and the tendencies of your users. This post demonstrates a very naive strategy: never remove items from the cache. If there is sufficient interest then I might write another blog post that demonstrates and compares the strategies mentioned above.

See http://en.wikipedia.org/wiki/Cache_algorithms for more details on caching strategies.

By: Bjorn

Bjorn — Mon, 18 Jan 2010 03:05:45 +0000

Nice disclaimer:
If you have many more items or larger images you will want to be more careful over selecting which items to cache and figuring out when to clear them from the cache.

Have you figured out any smart new approaches if your fall in to that category.?