Recently, in my email:
Makes sense, sounds like there's a wiki entry behind this one.
Dustin, would you mind putting something up there to describe how our memory gets allocated and where?
On Fri, Nov 12, 2010 at 3:21 PM, Dustin Sallings <firstname.lastname@example.org> wrote:
On Nov 12, 2010, at 14:57, Perry Krug wrote:
That's what I thought...
Is there anything we can do to make it clearer to the user that this isn't happening? Is there a stat for "too_small" or is it just rolled into the eject_failures?
There's really nothing there that can do that easily. In this case, all of the items are paged out, but just knowing about them takes up a lot of memory.
We've got some plans to have knowing take less memory. We could go a step further and move some of the paged out stuff to a bloom filter when we get even further in. I think there are a few customer cases we need to shake out of this one.