Timestamp creation has a performance impact on the Prometheus receiver in high-traffic environments.

[LukaszByczynski]

Component(s)

receiver/prometheus

Describe the issue you're reporting

Prometheus 3.0 scraper, introduced in the otel-collector 0.120.0, has the timestamp creation option set to true by default (see source).

Setting this option to true has performance implications in high-traffic environments. We observed some performance degradation in our high-traffic DaemonSet deployments due to this option. After analyzing CPU usage with a profiler, we found that timestamp creation is responsible for the performance drop. In our case, we don't need this option, so I created a PR to allow control of this option via a configuration flag.

[github-actions]

Pinging code owners:

• receiver/prometheus: @Aneurysm9 @dashpole @ArthurSens @krajorama

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[dashpole]

Looks related to #40245. Possibly a dup

[ArthurSens]

Yep, indeed a duplicate of #40245. I'm closing this issue so we keep the discussions in a single place, I hope that's ok!