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.

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

Difference between jemalloc_active_bytes and node memory #13610

Closed
fuyufjh opened this issue Nov 23, 2023 · 4 comments
Closed

Difference between jemalloc_active_bytes and node memory #13610

fuyufjh opened this issue Nov 23, 2023 · 4 comments
Labels
type/bug Something isn't working
Milestone

Comments

@fuyufjh
Copy link
Member

fuyufjh commented Nov 23, 2023

Observed from longevity test OOM.

image

For example, at 2023-11-21 22:59:00

  • jemalloc_allocated_bytes: 8.59 GB
  • jemalloc_active_bytes: 9.93 GB
  • Node memory (RSS): 12.3 GB

Difference is 2.37 GB.

Previous a very similiar issue #9669 has been solved by #9795

@github-actions github-actions bot added this to the release-1.5 milestone Nov 23, 2023
@fuyufjh
Copy link
Member Author

fuyufjh commented Nov 23, 2023

JVM is not used in longevity test.

image

@fuyufjh fuyufjh added the type/bug Something isn't working label Nov 23, 2023
@fuyufjh
Copy link
Member Author

fuyufjh commented Nov 24, 2023

Since I have no better ideas, now I am trying to manage the LRU watermark according to the system resident memory (rss) instead of Jemalloc's statistics.

Code: main...eric/try_manage_memory_by_rss

Test run: https://buildkite.com/risingwave-test/longevity-test/builds/816

The test was succeeded because the MemoryManager managed to controller the memory at around 7.5GB

JemallocMemoryControl { threshold_stable: 7816840478, threshold_graceful: 8933531975, threshold_aggressive: 10050223472 }

@yuhao-su
Copy link
Contributor

#13648 (comment)

@fuyufjh
Copy link
Member Author

fuyufjh commented Nov 29, 2023

Resolved by #13648

@fuyufjh fuyufjh closed this as completed Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants