Thanks for the thoughts. I don’t think it’s a huge concern to have a growing entity store for a few reasons. 1) The entities are stored in an indexed manner, so lookups are quick regardless. 2) If you think about it, even a dozen entities with 1000 rows consuming 1kb each would only take up ~10mb, which would be comparable to a page showing a dozen images. 3) Hard page refreshes will clear the store. However, I do think it’s a valid concern and I think it’s the responsible thing to provide an interface to address the potential for a large memory footprint, so I’ve made an issue to add a method to clear the database. Please take a look and share your thoughts on the issue thread.