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

Better calculate high/low watermarks for large RAM systems

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.8.1, 2.0, 2.0.1
    • Fix Version/s: feature-backlog
    • Component/s: couchbase-bucket
    • Security Level: Public
    • Labels:
      None
    • Triage:
      Untriaged
    • Is this a Regression?:
      Yes

      Description

      Our current method of taking 60% and 75% of RAM for low/high watermarks leaves us with lots of wasted space on systems with larger amounts of RAM (16GB+).

      I would propose a default of 5GB below max for high water mark and 10GB below max for low watermark for any bucket allocation over 16GB. That will make it only really kick in for 32GB systems.

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

        Activity

        Hide
        sharon Sharon Barr (Inactive) added a comment -

        low water mark is 65%, not 60%, and agree that for large memory systems (and we start seeing those in use) we need an adaptive algorithm (65% or no more then 10G, 75% or no more then 5G).

        Does it sounds good?

        Show
        sharon Sharon Barr (Inactive) added a comment - low water mark is 65%, not 60%, and agree that for large memory systems (and we start seeing those in use) we need an adaptive algorithm (65% or no more then 10G, 75% or no more then 5G). Does it sounds good?
        Show
        chiyoung Chiyoung Seo added a comment - http://www.couchbase.com/issues/browse/MB-5220
        Hide
        perry Perry Krug added a comment -

        These are not duplicate issues. MB-5220 asks simply to raise the watermark percentages...MB-4249 asks for a better method of calculation since any percentage will not be application to both large and small RAM systems.

        Show
        perry Perry Krug added a comment - These are not duplicate issues. MB-5220 asks simply to raise the watermark percentages... MB-4249 asks for a better method of calculation since any percentage will not be application to both large and small RAM systems.
        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
        perry Perry Krug added a comment -

        Dipti, can this be assigned to an upcoming release closer than .next?

        Show
        perry Perry Krug added a comment - Dipti, can this be assigned to an upcoming release closer than .next?
        Hide
        dipti Dipti Borkar added a comment -

        Investigate options for watermark selection in the 2.1 time frame

        Show
        dipti Dipti Borkar added a comment - Investigate options for watermark selection in the 2.1 time frame
        Hide
        maria Maria McDuff (Inactive) added a comment -

        We need to consider for 3.0

        Show
        maria Maria McDuff (Inactive) added a comment - We need to consider for 3.0
        Hide
        chiyoung Chiyoung Seo added a comment -

        Moving this to post 3.0 given the 3.0 release schedule and its scope.

        Show
        chiyoung Chiyoung Seo added a comment - Moving this to post 3.0 given the 3.0 release schedule and its scope.

          People

          • Assignee:
            chiyoung Chiyoung Seo
            Reporter:
            perry Perry Krug
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:

              Gerrit Reviews

              There are no open Gerrit changes