test SPSC queue #2
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @rezabrizi : First of all thanks for creating this github repo, It gave me very good introduction to lock free programming.
On this similar principle I wrote a pretty simple SPSC lock free queue, which also uses block version number concept to protecting read and write.
In summary following is the logic of my SPSC queue:
When I ran benchmark , I see my queue is able to produce ~120 millions messages, whereas your SPMC queue(tested only 1 producer and 1 consumer ) is able to generate ~500+ millions messages during the same 5 seconds of run.
Could you kindly check my source code(hardly 60 lines) and provide your valuable insight on where my queue is suffering from performance bottleneck ?