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

Will too much lager log lead to CPU arise? #533

Open
Ami-Kawashima opened this issue Dec 23, 2020 · 2 comments
Open

Will too much lager log lead to CPU arise? #533

Ami-Kawashima opened this issue Dec 23, 2020 · 2 comments

Comments

@Ami-Kawashima
Copy link

Recently,I have a erlang gateway project in rancher. One pod' CPU arise, alive, can't be accessed in.
Last year, I have used tsung to test it, one lager log cause -66%, two -82%.
Is there any idea or infomation? thank you.

@jadeallenx
Copy link
Member

Writing to the console is generally more CPU intensive than writing to disk files so make sure you’re not logging to the console.

That being said, depending on the quantity of log messages there can be an overhead that is measurable - you may want to consider logging messages at a higher severity level or removing log messages that are no longer necessary for general operation of the application

@Ami-Kawashima
Copy link
Author

Writing to the console is generally more CPU intensive than writing to disk files so make sure you’re not logging to the console.

That being said, depending on the quantity of log messages there can be an overhead that is measurable - you may want to consider logging messages at a higher severity level or removing log messages that are no longer necessary for general operation of the application

Thankyou. I'm logging to the /logs/console.log. I will send log to elk later and try to resolve that issue.

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