jemalloc.github.io/index.html at master · jemalloc/jemalloc.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
<!DOCTYPE html>
<html>

  <head>
    <meta charset='utf-8'>
    <meta http-equiv="X-UA-Compatible" content="chrome=1">
    <meta name="description" content="jemalloc : memory allocator">

    <link rel="stylesheet" type="text/css" media="screen" href="stylesheets/stylesheet.css">

    <title>jemalloc</title>
  </head>

  <body>

    <!-- HEADER -->
    <div id="header_wrap" class="outer">
        <header class="inner">
          <a id="forkme_banner" href="https://github.com/jemalloc">View on GitHub</a>

          <h1 id="project_title">jemalloc</h1>
          <h2 id="project_tagline">memory allocator</h2>

        </header>
    </div>

    <!-- MAIN CONTENT -->
    <div id="main_content_wrap" class="outer">
      <section id="main_content" class="inner">
        <p>jemalloc is a general purpose malloc(3) implementation that emphasizes
fragmentation avoidance and scalable concurrency support.  jemalloc first came
into use as the FreeBSD libc allocator in 2005, and since then it has found its
way into numerous applications that rely on its predictable behavior.  In 2010
jemalloc development efforts broadened to include developer support features
such as heap profiling and extensive monitoring/tuning hooks.  Modern jemalloc
releases continue to be integrated back into FreeBSD, and therefore versatility
remains critical.  Ongoing development efforts trend toward making jemalloc
among the best allocators for a broad range of demanding applications, and
eliminating/mitigating weaknesses that have practical repercussions for real
world applications.</p>

<h3>Documentation</h3>
<p>jemalloc has evolved substantially over its lifetime, so although the older
documentation is still broadly informative, many of the details are
obsolete.
<ul>
  <li> <p> <b><a href="jemalloc.3.html">jemalloc(3) manual page</a>:</b> The manual page fully describes the API and options supported by jemalloc, and includes a brief summary of its internals. </p> </li>
  <li> <p> <b><a href="https://github.com/jemalloc/jemalloc/wiki">Wiki</a>:</b> The wiki contains miscellaneous documentation such as links to <a href="https://github.com/jemalloc/jemalloc/wiki/Background#additional-documentation">papers and presentations</a>, FAQ answers, and tutorials. </p> </li>
</ul>
</p>

<h3>Project activity</h3>
<p>The jemalloc project is managed on <a href="https://github.com/jemalloc/jemalloc">GitHub</a>.  In order of increasing interest level, the following are useful entry points:
<ul>
  <li> <p> <b><a href="https://github.com/jemalloc/jemalloc/releases.atom">Releases atom feed</a>:</b> Track <a href="https://github.com/jemalloc/jemalloc/releases">releases</a> using an atom feed reader of your choice. </p> </li>
  <li> <p> <b><a href="https://github.com/jemalloc/jemalloc">Primary jemalloc repository</a>:</b> This is the primary jemalloc repository, with a small set of active branches including:
    <ul>
      <li> <p> <b><a href="https://github.com/jemalloc/jemalloc/tree/master">master</a>:</b> The master branch tracks stable releases. </p> </li>
      <li> <p> <b><a href="https://github.com/jemalloc/jemalloc/tree/dev">dev</a>:</b> The dev branch tracks current development, and at any given time may not be production-ready. </p> </li>
      <li> <p> <b><a href="https://github.com/jemalloc/jemalloc/tree/stable-3">stable-3</a>/<a href="https://github.com/jemalloc/jemalloc/tree/stable-4">stable-4</a>:</b> The stable-* branches are bugfix-only branches based on the last releases for previous major versions.  The versioned release history is linear, but relevant fixes may continue to be applied to the stable-* branches indefinitely. </p> </li>
    </ul>
    </p> </li>
  <li> <p> <b><a href="https://github.com/jemalloc/jemalloc/issues">Issues</a>:</b> The issue tracking system is used for all formal communication, including feature, bug, and release tracking, as well as questions (the <a href="https://github.com/jemalloc/jemalloc/issues?utf8=%E2%9C%93&q=label%3Aquestion%20">question</a> label is added during triage).  As a starting point, see <a href="https://github.com/jemalloc/jemalloc/milestones">milestones</a>, aka future releases. </p> </li>
  <li> <p> <b><a href="https://github.com/jemalloc/jemalloc/subscription">Development activity subscription</a>:</b> Watch all development activity via GitHub notifications. </p> </li>
  <li> <p> <b><a href="https://gitter.im/jemalloc/jemalloc">Gitter</a>:</b> Day-to-day chatter focused on jemalloc development.  The primary jemalloc developers conduct much of their informal communication here; feel welcome to observe and/or join in.</p> </li>
</ul>

<h4>Legacy</h4>
<p> The <a href="mailman/jemalloc-announce/index.html">jemalloc-announce</a> and <a href="mailman/jemalloc-discuss/index.html">jemalloc-discuss</a> mailing lists were retired in September 2016, but their archives remain available here.</p>

      </section>
    </div>

    <!-- FOOTER  -->
    <div id="footer_wrap" class="outer">
      <footer class="inner">
        <p>Published with <a href="https://pages.github.com">GitHub Pages</a></p>
      </footer>
    </div>
    <!-- Gitter sidecar -->
    <script>
      ((window.gitter = {}).chat = {}).options = {
        room: 'jemalloc/jemalloc'
      };
    </script>
    <script src="https://sidecar.gitter.im/dist/sidecar.v1.js" async defer></script>
  </body>
</html>