-
Notifications
You must be signed in to change notification settings - Fork 21
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
Chady Kamar #9
Open
chadykamar
wants to merge
6
commits into
MathieuNls:master
Choose a base branch
from
chadykamar:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Chady Kamar #9
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
5bb20a3
87ms without concurrency
chadykamar d820bfa
Parallelized with goroutines 62ms
chadykamar 20f022d
Use strings.TrimSuffix to remove bracket and extract function names
chadykamar aa69b14
Correct regex to allow for one character function names
chadykamar 2120ef5
Benchmarks for different concurrency schemes
chadykamar 5041cf9
Settled on the fastest scheme
chadykamar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel this is a bit strange optimization, starting a goroutine to increment a variable seems counterproductive as the cost of switching context between the different tasks will likely be higher than doing the operation locally (assuming you have more goroutines than cores).
Also, the channels you use are unbuffered, this means that goroutines who want to write concurrently on the channel will have to wait for the input of another to be consumed by this routine before it can continue executing.
All in all, while parallellizing the computations on different files at once is likely a cause for improvement in speed, I feel that the other routines are wasted resources as they likely do too little to bring real improvements in performance.
I may however be wrong, if you are able to provide benchmarks to justify these small routines, I'd be happy to take a look at them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do get better results this way. Just to clarify, are you referring to the 5 goroutines which do the incrementing/appending or the fact that I spawn a goroutine to process every line? My basic reasoning for spawning a routine for every line was that appending to a slice and inserting into a map can be expensive so I would rather not wait for the result to be computed to continue processing the incoming lines. The 5 routines and their respective channels are just an (ever so slightly faster) alternative to mutexes in this case.