You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project is published as tikv-jemallocator and jemallocator for historical reasons. The two crates are the same except names. It's OK to use either crate. But due to lack of permissions, only jemallocator and jemalloc-sys are updated. If you want to use other crates, tikv-xxx versions are still required.
To me, this reads like "use jemallocator over tikv-jemallocator" (maybe incorrectly so!), but if i further, it tells me to use tikv-jemallocator = "0.5". We've discussed in the team and we're confused if we're using the correct crate. Would it be possible to disambiguate the readme paragraph further to make it easier to follow what current best practice is?
The text was updated successfully, but these errors were encountered:
Currently, the crate we don't have permission to publish is jemallocator-global. So if you need it, then you have to use tikv-jemallocator-global and then all the dependencies will go to tikv-xxx. If you don't need it, choose whichever you like.
I recommend changing the README to clarify things, as @konstin suggested. In fact, until you have permission to publish every jemalloc* crate, I would recommend suggesting tikv-jemalloc* everywhere, because that's easier to understand.
The readme says:
To me, this reads like "use
jemallocator
overtikv-jemallocator
" (maybe incorrectly so!), but if i further, it tells me to usetikv-jemallocator = "0.5"
. We've discussed in the team and we're confused if we're using the correct crate. Would it be possible to disambiguate the readme paragraph further to make it easier to follow what current best practice is?The text was updated successfully, but these errors were encountered: