Skip to content

Reduce amount of locking on every created log event #4380

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

Open
wants to merge 1 commit into
base: feat/log-batching-separate-executor-service
Choose a base branch
from

Conversation

adinauer
Copy link
Member

@adinauer adinauer commented May 8, 2025

#skip-changelog

📜 Description

Reduce amount of locking on every created log event

💡 Motivation and Context

Previously every created log event would acquire the lock to check if it had to schedule.

💚 How did you test it?

📝 Checklist

  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

Copy link
Contributor

github-actions bot commented May 8, 2025

Messages
📖 Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against c639bfc

Copy link
Contributor

github-actions bot commented May 8, 2025

Performance metrics 🚀

  Plain With Sentry Diff
Startup time 405.51 ms 453.51 ms 48.00 ms
Size 1.58 MiB 2.08 MiB 508.47 KiB

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants