Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-26277

allow to have compressed data in RAM

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Trivial - P5 Trivial - P5
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Storage Execution

      Current situation: Having compression enabled - data size = 5 GB, storage size = 1GB
      But when data is loaded to RAM, it consumes 5 GB in RAM.

      Proposal:
      What if the data /working set/ in RAM would be compressed, same as on disk ? So working set in RAM would be 1 GB and not 5GB

      Considering a lot of CPUs, the online decompression overhead would be minor.

      This would not be of course suitable for super-fast data, but majority of the apps in my company is midsize,low-speed apps. With memory-compression switch we could avoid many situations when working set is above cache and pages must be exchanged with disk and locking the db

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            marian.badinka@dhl.com marian badinka
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: