Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-11059

don't build the server with jemalloc

Details

    Description

      We haven't seen any noticeable speed improvements from building the server with jemalloc. And we did have user complains about inability to use other memory allocators with MariaDB. But TokuDB (and, possibly, RockDB) need jemalloc for a good performance.

      A solution could be:

      • do not build with jemalloc
      • add malloc-liib=jemalloc to tokudb.cnf and manually add a jemalloc dependency to TokuDB packages
      • something similar should be done for systemd too
      • as TokuDB will now introduce an additional dependency that the server itself does not need, it will go into a separate rpm/deb package

      This way

      • the server will not be built with jemalloc, won't require or run with it
      • when a TokuDB package is installed, it will automatically bring in jemalloc as a dependency and will make the server use it — just as before
      • the user can always override it and use another memory allocator, if desired

      Attachments

        Issue Links

          Activity

            serg Sergei Golubchik created issue -
            serg Sergei Golubchik made changes -
            Field Original Value New Value
            Description We haven't seen any noticeable speed improvements from building the server with jemalloc. And we did have user complains about inability to use other memory allocators with MariaDB. But TokuDB (and, possibly, RockDB) need jemalloc for a good performance.

            A solution could be:
            * do not build with jemalloc
            * add {{malloc-liib=jemalloc}} to {{tokudb.cnf}} and manually add a jemalloc dependency to TokuDB packages
            * something similar should be done for systemd too
            * as TokuDB will now introduce an additional dependency that the server itself does not need, it will go into a separate rpm/deb package
            We haven't seen any noticeable speed improvements from building the server with jemalloc. And we did have user complains about inability to use other memory allocators with MariaDB. But TokuDB (and, possibly, RockDB) need jemalloc for a good performance.

            A solution could be:
            * do not build with jemalloc
            * add {{malloc-liib=jemalloc}} to {{tokudb.cnf}} and manually add a jemalloc dependency to TokuDB packages
            * something similar should be done for systemd too
            * as TokuDB will now introduce an additional dependency that the server itself does not need, it will go into a separate rpm/deb package

            This way the server will not be built with jemalloc, won't require or run with it. When a TokuDB package is installed, it will automatically bring in jemalloc as a dependency and will make the server use it — just as it was before
            serg Sergei Golubchik made changes -
            Description We haven't seen any noticeable speed improvements from building the server with jemalloc. And we did have user complains about inability to use other memory allocators with MariaDB. But TokuDB (and, possibly, RockDB) need jemalloc for a good performance.

            A solution could be:
            * do not build with jemalloc
            * add {{malloc-liib=jemalloc}} to {{tokudb.cnf}} and manually add a jemalloc dependency to TokuDB packages
            * something similar should be done for systemd too
            * as TokuDB will now introduce an additional dependency that the server itself does not need, it will go into a separate rpm/deb package

            This way the server will not be built with jemalloc, won't require or run with it. When a TokuDB package is installed, it will automatically bring in jemalloc as a dependency and will make the server use it — just as it was before
            We haven't seen any noticeable speed improvements from building the server with jemalloc. And we did have user complains about inability to use other memory allocators with MariaDB. But TokuDB (and, possibly, RockDB) need jemalloc for a good performance.

            A solution could be:
            * do not build with jemalloc
            * add {{malloc-liib=jemalloc}} to {{tokudb.cnf}} and manually add a jemalloc dependency to TokuDB packages
            * something similar should be done for systemd too
            * as TokuDB will now introduce an additional dependency that the server itself does not need, it will go into a separate rpm/deb package

            This way
            * the server will not be built with jemalloc, won't require or run with it
            * when a TokuDB package is installed, it will automatically bring in jemalloc as a dependency and will make the server use it — just as before
            * the user can always override it and use another memory allocator, if desired
            elenst Elena Stepanova made changes -
            Labels 10.2-ga
            serg Sergei Golubchik made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            serg Sergei Golubchik made changes -
            Status In Progress [ 3 ] Stalled [ 10000 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.2.5 [ 22117 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            elenst Elena Stepanova made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 77836 ] MariaDB v4 [ 132969 ]

            People

              serg Sergei Golubchik
              serg Sergei Golubchik
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.