patrickdung2022 opened a new issue, #47167:
URL: https://github.com/apache/doris/issues/47167

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Version
   
   3.0.3
   
   ### What's Wrong?
   
   In the admin manual:
   
https://doris.apache.org/docs/3.0/admin-manual/trouble-shooting/memory-management/memory-analysis/jemalloc-memory-analysis
   
   It is mentioned that 
   Reduce dirty_decay_ms of JEMALLOC_CONF in be.conf to 2000 ms or less. The 
default dirty_decay_ms in be.conf is 5000 ms. Jemalloc will release dirty pages 
according to a smooth gradient curve within the time specified by 
dirty_decay_ms. For reference, [Jemalloc 
opt.dirty_decay_ms](https://jemalloc.net/jemalloc.3.html#opt.dirty_decay_ms). 
When the BE process has insufficient available memory and triggers Minor GC or 
Full GC, it will actively release all dirty pages according to a certain 
strategy.
   
       Before Doris 2.1, the default value of dirty_decay_ms in JEMALLOC_CONF 
in be.conf is 15000, which will cause the Jemalloc Cache to be too large in 
some scenarios. After Doris 2.1, the default value is 5000.
   
   When compare below config (v2.1.7 and v3.0.3):
   https://github.com/apache/doris/blob/2.1.7-rc03/conf/be.conf
   https://github.com/apache/doris/blob/3.0.3-rc04/conf/be.conf
   
   It is found that v2.1.7 has updated JEMALLOC_CONF to 
muzzy_decay_ms:5000,dirty_decay_ms:5000
   But the same setting in v3.0.3 is still 
muzzy_decay_ms:15000,dirty_decay_ms:15000
   
   Does Doris version 3.0.x actually needs to update these settings to 5000?
   
   ### What You Expected?
   
   Setting same as manual
   
   ### How to Reproduce?
   
   _No response_
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to