-
-
Notifications
You must be signed in to change notification settings - Fork 444
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
Crons lead to unusual 10% load increase #3165
Comments
@Angelodaniel do you know if other Sentry annotations have been used before (e.g. I'll try to reproduce and see if there's something we can do about it. |
@Angelodaniel is there only a single |
@Angelodaniel does this only happen when the server has been running for a while or can it be observed immediately? |
@Angelodaniel is the method annotated with sorry for the many separate messages |
As a workaround, you could try to use If that alone doesn't work, you might have to combine it with |
Hello, I can jump in here and answer your questions @Angelodaniel
Only the @SentryCheckIn was used.
@Angelodaniel does this only happen when the server has been running for a while or can it be observed immediately?
|
@stockii thank you for your answers, we'll investigate and report back here. |
@stockii so far I haven't been able to confirm the load increase on our Spring Boot 3 sample. Have you had any luck with the workaround in #3165 (comment) ? |
Integration
sentry-spring-boot-starter-jakarta
Java Version
Spring boot 3.2.2
Version
7.2.0
Steps to Reproduce
spring boot application 3.2.2
annotation: @SentryCheckIn(value = "x", heartbeat = true)
SDK version: io.sentry:sentry-spring-boot-starter-jakarta:7.2.0
Looks like that the gc_memory_promoted_bytes_total is much higher than usual
Expected Result
Not a big increase in load increase
Actual Result
I’ve noticed that enabling the cron SDK in our Spring Boot application leads to an unusual 10% load increase on one of the three instances in our cluster. This behavior is apparent even when the scheduler isn’t active, as it’s set to run in the morning.
![Screenshot 2024-01-25 at 15 18 29](https://private-user-images.githubusercontent.com/25929053/299699988-b8e243ac-b817-4132-a5a2-dcab91c803b4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5NzQ0NTksIm5iZiI6MTczODk3NDE1OSwicGF0aCI6Ii8yNTkyOTA1My8yOTk2OTk5ODgtYjhlMjQzYWMtYjgxNy00MTMyLWE1YTItZGNhYjkxYzgwM2I0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDAwMjIzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM4MDM4MThiYzhmNTZhOWY4MTFiMzYzODA1OThkMDFmY2UzM2JkNTMzMTdhMjNhNmViZjk1MmEyMzJjNGUwYzQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.W-sLdkF77fykLcIGBKT1IGC-RgNPaXps6femamHS4Lg)
┆Issue is synchronized with this Jira Improvement by Unito
The text was updated successfully, but these errors were encountered: