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

The Tuned process occupies a lot of inactive anon memory #724

Open
muxin96 opened this issue Jan 7, 2025 · 2 comments
Open

The Tuned process occupies a lot of inactive anon memory #724

muxin96 opened this issue Jan 7, 2025 · 2 comments

Comments

@muxin96
Copy link

muxin96 commented Jan 7, 2025

tuned version: 2.19.0-1.el8
python3 version:3.6.8

The memory of tuned process exceeds 2GB,and the memory has not been released. Through memory.stat, the main memory occupancy is inactive anon. And the file of tune.log stay at 2023. Through the strace and stack, the tuned stack at do_select(), and also call select() frequently by stracing.

Does this tuned version have any user-space memory leaks?
归档.zip

@zacikpa
Copy link
Contributor

zacikpa commented Jan 7, 2025

Hi, in TuneD versions before 2.24.0, there was a bug that caused TuneD to accumulate (not leak) memory with each profile change. If TuneD was kept running for, e.g., 8 months with a profile change every hour, the accumulated memory could get to 2GB. This was fixed in #666.

@muxin96
Copy link
Author

muxin96 commented Jan 8, 2025

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants