CPU Usage 100% for a while after massive log outputted.
This is our servers memory usages before and after this commit (fixed in 01/21). serilog-sinks-fluentd v0.4.0 has memory leak problem in serialization. But I couldn't fix by the solution in Issue #22. Finally, I changed serialization library from MsgPack.Cli to MessagePack for C# and confirmed the memory leak is fixed.
In addition, I also fixed the performance problem because MessagePack for C# said "It is 10x faster than MsgPack-Cli".
Attention, MessagePack for C# is not compatible 100% for MsgPack-Cli. It need to change TargetFramework. And it may convert enum in logEvent.Properties to int instead of string. In our case it is no problem. But I don't know in your case.
This PR fixes the following problems:
22
This is our servers memory usages before and after this commit (fixed in 01/21). serilog-sinks-fluentd v0.4.0 has memory leak problem in serialization. But I couldn't fix by the solution in Issue #22. Finally, I changed serialization library from MsgPack.Cli to MessagePack for C# and confirmed the memory leak is fixed.
In addition, I also fixed the performance problem because MessagePack for C# said "It is 10x faster than MsgPack-Cli".
Attention, MessagePack for C# is not compatible 100% for MsgPack-Cli. It need to change TargetFramework. And it may convert enum in logEvent.Properties to int instead of string. In our case it is no problem. But I don't know in your case.