-
Notifications
You must be signed in to change notification settings - Fork 0
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
Runtime Events OpenTelemetry Experiment #2
base: pr_target
Are you sure you want to change the base?
Conversation
After discussion, I THINK we came to the conclusion that events are sent in order by timestamp. This means that we can assume if we receive an event with a timestamp that is greater than a given activity's stop timestamp, we will no longer need the activity in the cache. We can use this to flush the cache of activities no longer needed every X number of events. |
This is true for all the events on the runtime's native provider (which includes JIT and GC events), but just for clarity you could still see other kinds of events with timestamps that are out of order relative to the native provider events. |
No description provided.