Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

update jemalloc version #168

Closed
silence-coding opened this issue Mar 25, 2021 · 1 comment
Closed

update jemalloc version #168

silence-coding opened this issue Mar 25, 2021 · 1 comment

Comments

@silence-coding
Copy link

silence-coding commented Mar 25, 2021 •
edited
Loading

A strange situation occurs in a service in our environment, where the memory increases by 1 GB in the case of no load. The service is developed using Tokio. The current jemallocator version is 0.3. 0, and the jemalloc version carried by the service is 5.1.0.

Version 5.1.0 has a terrible problem
jemalloc/jemalloc#1497
@0xdeafbeef 0xdeafbeef mentioned this issue Sep 3, 2021
Merged
@zhangsoledad zhangsoledad mentioned this issue Sep 8, 2021
Merged
bors bot added a commit to nervosnetwork/ckb that referenced this issue Sep 9, 2021
@bors @zhangsoledad
Merge #3023
b3da297 
3023: perf: switch global alloc to tikv-jemallocator r=doitian,driftluo a=zhangsoledad

<!--
Thank you for contributing to nervosnetwork/ckb!

If you haven't already, please read [CONTRIBUTING](https://github.com/nervosnetwork/ckb/blob/develop/CONTRIBUTING.md) document.

If you're unsure about anything, just ask; somebody should be along to answer within a day or two.

PR Title Format:
1. module [, module2, module3]: what's changed
2. *: what's changed
-->

### What problem does this PR solve?

gnzlbg/jemallocator#168
jemalloc/jemalloc#1497
see also: rust-lang/rust#83152

### What is changed and how it works?

Proposal:  switch global alloc to tikv-jemallocator which is more up-to-date

### Related changes


### Check List <!--REMOVE the items that are not applicable-->

Side effects

- Performance regression
- Breaking backward compatibility

### Release note <!-- Choose from None, Title Only and Note. Bugfixes or new features need a release note. -->

```release-note
Title Only: Include only the PR title in the release note.
```



Co-authored-by: zhangsoledad <787953403@qq.com>
@Haraade Haraade mentioned this issue May 24, 2022
Closed
@silence-coding
Copy link
Author

Use tikv instead.
https://github.com/tikv/jemallocator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@silence-coding