Hi Team,
While load-testing my application, i am seeing issues with my lager application, consuming huge memory. The process is getting consumed a lot and its reaching GB's while monitoring with observer we identified it. Below mentioned are extra shinks
{proxy_lager_event, [
{handlers, [
{lager_file_backend, [
{file, "log/raw/XXX.txt"},
{level, info},
{rotator, lager_rotator},
{date, "$D23H59"},
{count, 60},
{formatter_config, [date, " ", time, " ", message, {eol, "\r\n"}]}
]}
]},
{async_threshold, 500},
{async_threshold_window, 50}
]},
{handler_lager_event, [
{handlers, [
{lager_file_backend, [
{file, "log/raw/XXX.txt"},
{level, info},
{rotator, eutils_lager_rotator},
{date, "$D23H59"},
{count, 60},
{formatter_config, [date, " ", time, " ", message, {eol, "\r\n"}]}
]}
]},
{async_threshold, 500},
{async_threshold_window, 50}
]},
We put a async_threshold of 500 messages. can this be quite high.
Can you suggest how can we better use lager(we are using tag 3.7.0)
Hi Team,
While load-testing my application, i am seeing issues with my lager application, consuming huge memory. The process is getting consumed a lot and its reaching GB's while monitoring with observer we identified it. Below mentioned are extra shinks
{proxy_lager_event, [
{handlers, [
{lager_file_backend, [
{file, "log/raw/XXX.txt"},
{level, info},
{rotator, lager_rotator},
{date, "$D23H59"},
{count, 60},
{formatter_config, [date, " ", time, " ", message, {eol, "\r\n"}]}
]}
]},
{async_threshold, 500},
{async_threshold_window, 50}
]},
{handler_lager_event, [
{handlers, [
{lager_file_backend, [
{file, "log/raw/XXX.txt"},
{level, info},
{rotator, eutils_lager_rotator},
{date, "$D23H59"},
{count, 60},
{formatter_config, [date, " ", time, " ", message, {eol, "\r\n"}]}
]}
]},
{async_threshold, 500},
{async_threshold_window, 50}
]},
We put a async_threshold of 500 messages. can this be quite high.
Can you suggest how can we better use lager(we are using tag 3.7.0)