typesense / typesense/typesense

jemalloc alternative?

Open
#1,913 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
26.6k
Forks
973
Avg merge
18h 45m
Merged PRs (30d)
4

Description

Description

Hi, I was wondering if you ever consider removing a dependency on jemalloc in your code. It would be cool to have memory allocator pluggable. Right now I'm evaluating a possibility of using https://github.com/microsoft/mimalloc and having to use LD_LIBRARY_PRELOAD hack when you can just use it natively seems weird. Also, even when using preloading jemalloc's code is being ran anyway.

Would you consider a PR in this case?

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. Start by locating where the jemalloc dependency is declared and initialized, then determine how allocator selection could be made pluggable; done would mean a supported alternative such as mimalloc works natively without LD_LIBRARY_PRELOAD and jemalloc does not run when another allocator is selected.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.