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
Because of the nature of Go maps, iterating the subscribe set means a fair number
of subMapMutex.Lock(), Unlock() calls
It might be cleaner to translate the subscriber uniq id to an array/slice index, which
then gets iterated, skipping empties.
The text was updated successfully, but these errors were encountered:
cameronelliott
changed the title
Remove the many subMapMutex.Lock(), Unlock() calls
Remove the many subMapMutex.Lock(), Unlock() calls, possibly
Apr 17, 2021
Because of the nature of Go maps, iterating the subscribe set means a fair number
of subMapMutex.Lock(), Unlock() calls
It might be cleaner to translate the subscriber uniq id to an array/slice index, which
then gets iterated, skipping empties.
The text was updated successfully, but these errors were encountered: