Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-2817

As a curious membase user, I understand how memory is allocated and where it's used so that I can make better decisions.

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 2.0
    • Fix Version/s: 3.0
    • Component/s: couchbase-bucket
    • Security Level: Public
    • Labels:
      None

      Description

      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?

      Perry

      On Fri, Nov 12, 2010 at 3:21 PM, Dustin Sallings <dustin@membase.com> 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.

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        peter peter added a comment -

        Please prioritize with other post 2.0 requirements.

        Show
        peter peter added a comment - Please prioritize with other post 2.0 requirements.
        Hide
        mikew Mike Wiederhold added a comment -

        I will add some documentation for this.

        Show
        mikew Mike Wiederhold added a comment - I will add some documentation for this.
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        per bug scrub
        deferring to 2.1

        Show
        farshid Farshid Ghods (Inactive) added a comment - per bug scrub deferring to 2.1
        Hide
        mikew Mike Wiederhold added a comment -

        This issue seems to be about adding better stats to get insight on memory usage. I haven't heard of anything specific recently and since this ticket is old I'm going to close it for now as incomplete.

        Show
        mikew Mike Wiederhold added a comment - This issue seems to be about adding better stats to get insight on memory usage. I haven't heard of anything specific recently and since this ticket is old I'm going to close it for now as incomplete.

          People

          • Assignee:
            mikew Mike Wiederhold
            Reporter:
            dustin Dustin Sallings (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2h
              2h
              Remaining:
              Remaining Estimate - 2h
              2h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Gerrit Reviews

                There are no open Gerrit changes