Skip to content

Conversation

SayantanScience
Copy link

Search.solution was unnecessarily synchronising its operations. The only part where it needs synchronisation is the init part. So, we add a (unsynchronized) check there. This will cause the first call in each thread to try to init, but only one thread will get the lock on CoordCube.class and init it. After this init phase, the process will become completely lock-free(actually this is the double-check idiom)

Search.solution was unnecessarily synchronising its operations. The only part where it needs synchronisation is the init part. So, we add a (unsynchronized) check there. This will cause the first call in each thread to try to init, but only one thread will get the lock on CoordCube.class and init it. After this init phase, the process will become completely lock-free(actually this is the double-check idiom)
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

Successfully merging this pull request may close these issues.

1 participant