You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: