Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

otel.instrumentation.reactor.enabled dramatacilly increases cpu usage #13261

Open
Tiberius202 opened this issue Feb 10, 2025 · 2 comments
Open
Labels
needs author feedback Waiting for additional feedback from the author stale

Comments

@Tiberius202
Copy link

Describe the bug

The "otel.instrumentation.reactor.enabled" flag dramatically increases the cpu usage of the java app.

Steps to reproduce

Run performance tests on Java program with Java agent with
otel.instrumentation.common.default-enabled=false
and
otel.instrumentation.reactor.enabled=true

Then run performance tests with
otel.instrumentation.reactor.enabled=true

Expected behavior

We expect cpu utilization in our testing to be around 35% with and without OTEL auto instrumentation.

Actual behavior

When we run OTEL instrumentation with this flag enabled (which is enabled by the defaults), we see CPU utilization is around 60%. We see a doubling of cpu utilization in all of our tests which include this instrumentation flag.

Javaagent or library instrumentation version

2.1.0

Environment

JDK:
openjdk 17.0.14 2025-01-21 LTS
OpenJDK Runtime Environment Corretto-17.0.14.7.1 (build 17.0.14+7-LTS)
OpenJDK 64-Bit Server VM Corretto-17.0.14.7.1 (build 17.0.14+7-LTS, mixed mode)
OS:
Alpine Linux v3.21.2
Spring Boot 3.3.7
OTEL 2.1.0 Java Agent
ECS Fargate single task with 8vcpu
Client load of 500 TPS with Hercules and JMeter

OTEL Settings:
otel.instrumentation.spring-boot-actuator-autoconfigure.enabled=true
otel.exporter.otlp.metrics.temporality.preference=DELTA
otel.javaagent.logging=application

Additional context

Thanks to [email protected] for finding this. He may have some more information and testing results.
cc: @akats7

@Tiberius202 Tiberius202 added bug Something isn't working needs triage New issue that requires triage labels Feb 10, 2025
@laurit
Copy link
Contributor

laurit commented Feb 11, 2025

A minimal sample that reproduces the issue could be helpful.

@steverao steverao added needs author feedback Waiting for additional feedback from the author and removed bug Something isn't working needs triage New issue that requires triage labels Feb 13, 2025
Copy link
Contributor

This has been automatically marked as stale because it has been marked as needing author feedback and has not had any activity for 7 days. It will be closed automatically if there is no response from the author within 7 additional days from this comment.

@github-actions github-actions bot added the stale label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs author feedback Waiting for additional feedback from the author stale
Projects
None yet
Development

No branches or pull requests

3 participants