Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enquiry : reasoning behind using a single mutex in sieve.go #38

Closed
SHIVAYspec opened this issue Aug 9, 2024 · 1 comment
Closed

Enquiry : reasoning behind using a single mutex in sieve.go #38

SHIVAYspec opened this issue Aug 9, 2024 · 1 comment

Comments

@SHIVAYspec
Copy link

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.

@scalalang2
Copy link
Owner

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 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants