On 12/15/23 06:01, Maksim Davydov wrote:No, it just seemed like a good idea to make a simple machine-readable
Provides per task split locks counter to monitor split locks rateHave you considered doing this with tracing instead?
in the system. It can be helpful in split locks monitoring to get a clear
sense of which process causing split locks and how many of them have
happened by the moment. For instance, it might be used by cloud providers
who can't control guest executable code and want to make decisions based
on the rate value like ratelimiting or notifing the split lock origins.
It seems a _little_ silly for everyone to pay the cost of having that
counter around.