We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
描述bug
实际业务量不多,但是内存占用高,需要定时重启,是不是内存没有回收。
复现
无
期望
希望能解决问题
截图
The text was updated successfully, but these errors were encountered:
@maidou758 你好!我是Dosu,一个可以帮助你解决 bug、回答问题,甚至成为贡献者的机器人。我会在等待人类维护者处理你的问题时帮助你。
I found a similar closed issue regarding high memory usage in Apollo, but no solution was found in the comments [1].
For monitoring and analyzing memory usage patterns in Apollo, you can enable client monitoring by configuring the following properties:
apollo.client.monitor.enabled
true
ConfigMonitor
apollo.client.monitor.jmx.enabled
apollo.client.monitor.external.type
prometheus
apollo.client.monitor.external.export-period
These configurations can help you gather and analyze memory usage patterns to identify potential issues [2].
Additionally, the default memory settings for Apollo's configuration service in version 1.7.1 are:
export JAVA_OPTS="-server -Xms6144m -Xmx6144m -Xss256k -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=384m -XX:NewSize=4096m -XX:MaxNewSize=4096m -XX:SurvivorRatio=18"
You might want to review these settings to see if they can be optimized for your specific use case [3].
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
Sorry, something went wrong.
No branches or pull requests
描述bug
实际业务量不多,但是内存占用高,需要定时重启,是不是内存没有回收。
复现
无
期望
希望能解决问题
截图
额外的细节和日志
The text was updated successfully, but these errors were encountered: