You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a heavily used server a lot of segments end at the same time, and from what see in the profiles this lock is a problem.
Can it be avoided at all? For instance, using some magic "per-thread" generator (as much as that is possible, but possibly just having more than one rand instance might work?)
If it cannot be avoided, can it be made smaller? I see that it uses defer to unlock, which means it unlocks after the conversion of the bits to the hex representation needed in the ID. Maybe it can be explicitly unlocked at least before that?
The text was updated successfully, but these errors were encountered:
go-agent/v3/internal/trace_id_generator.go
Lines 52 to 58 in 046b4fc
In a heavily used server a lot of segments end at the same time, and from what see in the profiles this lock is a problem.
defer
to unlock, which means it unlocks after the conversion of the bits to the hex representation needed in the ID. Maybe it can be explicitly unlocked at least before that?The text was updated successfully, but these errors were encountered: