We are currently storing many StoryCollections in the Cache. These lists
contain many duplicate stories and result in a relatively large memory
footprint and out of sync story state.
I am planning on a major refactoring of the cached stories:
- A story and related data will be stored in one object. (Story, tags,
comments, user kicks)
- Lists of stories will be stored as List<id> of story ids.
I'll also introduce some caching for the StoryList on the main feed - this
is what gets hit the most.
Original issue reported on code.google.com by gavinjo...@gmail.com on 14 Sep 2007 at 10:39
Original issue reported on code.google.com by
gavinjo...@gmail.com
on 14 Sep 2007 at 10:39