[Bugs] [Bug 1385758] [RFE] Support multiple bricks in one process (multiplexing)

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1385758



--- Comment #81 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/14763 committed in master by Vijay Bellur
(vbellur at redhat.com) 
------
commit 1a95fc3036db51b82b6a80952f0908bc2019d24a
Author: Jeff Darcy <jdarcy at redhat.com>
Date:   Thu Dec 8 16:24:15 2016 -0500

    core: run many bricks within one glusterfsd process

    This patch adds support for multiple brick translator stacks running
    in a single brick server process.  This reduces our per-brick memory usage
by
    approximately 3x, and our appetite for TCP ports even more.  It also
creates
    potential to avoid process/thread thrashing, and to improve QoS by
scheduling
    more carefully across the bricks, but realizing that potential will require
    further work.

    Multiplexing is controlled by the "cluster.brick-multiplex" global option. 
By
    default it's off, and bricks are started in separate processes as before. 
If
    multiplexing is enabled, then *compatible* bricks (mostly those with the
same
    transport options) will be started in the same process.

    Change-Id: I45059454e51d6f4cbb29a4953359c09a408695cb
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy at redhat.com>
    Reviewed-on: https://review.gluster.org/14763
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=E4K8YAiFL6&a=cc_unsubscribe