Giter Club home page Giter Club logo

jemalloc-feedstock's Introduction

About jemalloc

Home: http://jemalloc.net

Package license: BSD-2-Clause

Feedstock license: BSD-3-Clause

Summary: general purpose malloc(3) implementation

Development: https://github.com/jemalloc/jemalloc

Current build status

Azure
VariantStatus
linux_64 variant
linux_aarch64 variant
linux_ppc64le variant
osx_64 variant
osx_arm64 variant

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing jemalloc

Installing jemalloc from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, jemalloc, jemalloc-local, libjemalloc, libjemalloc-local can be installed with conda:

conda install jemalloc jemalloc-local libjemalloc libjemalloc-local

or with mamba:

mamba install jemalloc jemalloc-local libjemalloc libjemalloc-local

It is possible to list all of the versions of jemalloc available on your platform with conda:

conda search jemalloc --channel conda-forge

or with mamba:

mamba search jemalloc --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search jemalloc --channel conda-forge

# List packages depending on `jemalloc`:
mamba repoquery whoneeds jemalloc --channel conda-forge

# List dependencies of `jemalloc`:
mamba repoquery depends jemalloc --channel conda-forge

About conda-forge

Powered by NumFOCUS

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating jemalloc-feedstock

If you would like to improve the jemalloc recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/jemalloc-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

  • If the version of a package is not being increased, please add or increase the build/number.
  • If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

jemalloc-feedstock's People

Contributors

beckermr avatar conda-forge-admin avatar conda-forge-curator[bot] avatar github-actions[bot] avatar jakirkham avatar matthiasdiener avatar regro-cf-autotick-bot avatar sodre avatar wesm avatar xhochy avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

jemalloc-feedstock's Issues

Please delete jemalloc 5.0.0 builds from anaconda.org

@jakirkham @ocefpaf these builds are broken due to a glibc incompatibility. We are discussing with the jemalloc developers how to resolve this (jemalloc/jemalloc#937), but in the meantime, despite our efforts to pin the jemalloc version at 4.4.0 for some reason conda still wants to install 5.0.0

$ conda create -n arrow-conda-test python=3.6 pyarrow -c conda-forge
Fetching package metadata ...............
Solving package specifications: .

Package plan for installation in environment /home/wesm/anaconda3/envs/arrow-conda-test:

The following NEW packages will be INSTALLED:

    arrow-cpp:       0.4.1-np113py36_2  conda-forge
    ca-certificates: 2017.4.17-0        conda-forge
    certifi:         2017.4.17-py36_0   conda-forge
    jemalloc:        5.0.0-1            conda-forge
    mkl:             2017.0.1-0         defaults   
    ncurses:         5.9-10             conda-forge
    numpy:           1.13.0-py36_0      defaults   
    openssl:         1.0.2k-0           conda-forge
    pandas:          0.20.2-np113py36_1 conda-forge
    parquet-cpp:     1.2.0.pre-0        conda-forge
    pip:             9.0.1-py36_0       conda-forge
    pyarrow:         0.4.1-np113py36_0  conda-forge
    python:          3.6.1-3            conda-forge
    python-dateutil: 2.6.0-py36_0       conda-forge
    pytz:            2017.2-py36_0      conda-forge
    readline:        6.2-0              conda-forge
    setuptools:      33.1.1-py36_0      conda-forge
    six:             1.10.0-py36_1      conda-forge
    sqlite:          3.13.0-1           conda-forge
    tk:              8.5.19-1           conda-forge
    wheel:           0.29.0-py36_0      conda-forge
    xz:              5.2.2-0            conda-forge
    zlib:            1.2.11-0           conda-forge

in contrast

$ conda create -n arrow-conda-test python=3.6 arrow-cpp
Fetching package metadata ...............
Solving package specifications: .

Package plan for installation in environment /home/wesm/anaconda3/envs/arrow-conda-test:

The following NEW packages will be INSTALLED:

    arrow-cpp:       0.4.1-np113py36_3 conda-forge
    ca-certificates: 2017.4.17-0       conda-forge
    certifi:         2017.4.17-py36_0  conda-forge
    jemalloc:        4.4.0-0           conda-forge
    mkl:             2017.0.1-0        defaults   
    ncurses:         5.9-10            conda-forge
    numpy:           1.13.0-py36_0     defaults   
    openssl:         1.0.2k-0          conda-forge
    pip:             9.0.1-py36_0      conda-forge
    python:          3.6.1-3           conda-forge
    readline:        6.2-0             conda-forge
    setuptools:      33.1.1-py36_0     conda-forge
    sqlite:          3.13.0-1          conda-forge
    tk:              8.5.19-1          conda-forge
    wheel:           0.29.0-py36_0     conda-forge
    xz:              5.2.2-0           conda-forge
    zlib:            1.2.11-0          conda-forge

So the build 3 with pinned jemalloc is there, but the dependency resolver isn't doing the right thing, or I may not understand how the dependency pinning works

Static linking

Static libraries were removed in 56a05fd. Would it be possible to add jemalloc-static to re-enable static linking?

"Uniform prefixing" across platforms

I'm in a situation where I would like to use jemalloc as an "alternate"/"additional" allocator, while not overriding the system allocator. Given the package in its current state, that's hard, because on macOS, malloc will not be overridden, while on Linux, it will. Would you be open to adding an additional (conda) output to this package that has the je_ prefix across all platforms? If so, I'd be happy to try my hand at it in a PR.

cc @matthiasdiener @lukeolson

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.