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
Just an enquiry
What is the reason for using a single Mutex in sieve.go? Did you consider dividing it into shards and keeping one Mutex per shard?
It seems like it would decrease contention on the Mutex if the system has multiple processors.
Thanks for your time in advance.
The text was updated successfully, but these errors were encountered:
I had opened an issue related with your inquiry. #24
I won't be able to work on it right now, but I plan to develop it after September.
If you want to take this issue and contribute, then I would appreciate it 😄
Just an enquiry
What is the reason for using a single Mutex in sieve.go? Did you consider dividing it into shards and keeping one Mutex per shard?
It seems like it would decrease contention on the Mutex if the system has multiple processors.
Thanks for your time in advance.
The text was updated successfully, but these errors were encountered: