search

open-telemetry / opentelemetry-dotnet

The OpenTelemetry .NET Client
https://opentelemetry.io
Apache License 2.0
3.18k stars 753 forks source link

Log Stress test to follow recommended logging practise #5790

Closed cijothomas closed 1 month ago

cijothomas commented 1 month ago

Stress test modified to use what we recommend in getting started guides.

In case anyone is curious, this gets ~46 M/sec for the machine below:

 OS: Ubuntu 22.04.4 LTS (5.15.153.1-microsoft-standard-WSL2)
  Hardware: AMD EPYC 7763 64-Core Processor - 2.44 GHz, 16vCPUs,
  RAM: 64.0 GB
rajkumar-rangaraj commented 1 month ago

In case anyone is curious, this gets ~46 M/sec for the machine below

Just out of curiosity, have you run this with the current code to see what the difference in performance was?

cijothomas commented 1 month ago

In case anyone is curious, this gets ~46 M/sec for the machine below

Just out of curiosity, have you run this with the current code to see what the difference in performance was?

~55M/sec. The current code was logging the payload https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/test/OpenTelemetry.Tests.Stress.Logs/Payload.cs I don't fully recall why was it used originally, I didn't remove that class in this PR, so we can add it back as an option in the stress test (I guess we were using it to test the impact of large number of KV pairs when using the LogRecord pooling, but not sure...)