Hi, A kindly reminder :) If anyone can share some insights, or some way to reduce the impact of this contention.
Thanks, Tomer. ב-יום שני, 17 בינואר 2022 בשעה 09:32:14 UTC+2, Tomer Schwartz כתב/ה: > Hi, > > We are running a client-server load test with 500 concurrent users, and we > are seeing a high CPU on a SpinLock called > by Grpc.Core.Internal.CompletionRegistry.Register. > At average, this SpinLock is seen on 15% of the CPU frames under a > profiler. But during few seconds where we're seeing a significant increase > in latencies, the profiler shows that this SpinLock cost had an average > cost of ~80% of the CPU frames, and even 95% of the CPU frames: > [image: GrpcCore_SpinLock5.JPG] > > Is there any way to avoid this penalty? > I see that this SpinLock is protecting a Dictionary > of IOpCompletionCallbacks. Are those callbacks affected by anything that we > control in our code? > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/1c115b75-6671-44da-a04f-604105eac831n%40googlegroups.com.
