Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • omnibus-gitlab omnibus-gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 990
    • Issues 990
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 62
    • Merge requests 62
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • omnibus-gitlabomnibus-gitlab
  • Issues
  • #3073
Closed
Open
Created Dec 29, 2017 by Gabriel Mazetto@brodock🔴Developer

Consider a different version of jemalloc

Based on this article: https://www.speedshop.co/2017/12/04/malloc-doubles-ruby-memory.html

Do not use jemalloc 4.x with Ruby. It has a bad interaction with Transparent Huge Pages that reduces the memory savings you’ll see. Instead, use jemalloc 3.6. 5.0’s performance with Ruby is currently unknown.

They suggest we may have better memory footprint by either going back to 3.6 or moving up to 5.x

We are currently bundling 4.2.1 (check changes here: https://github.com/jemalloc/jemalloc/releases).

cc @stanhu @marin

Edited Dec 29, 2017 by Gabriel Mazetto
Assignee
Assign to
Time tracking