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

rust: Split project 4 into two projects #236

Open
brson opened this issue Jun 26, 2019 · 0 comments
Open

rust: Split project 4 into two projects #236

brson opened this issue Jun 26, 2019 · 0 comments
Labels

Comments

@brson
Copy link
Contributor

brson commented Jun 26, 2019

After #231 it has two basic goals: introduce multithreading, then remove locks from readers.

The project has twice the words of any other. It should be two different projects.

There's another question of the benchmarking section, which already carries a note about how complex it is. There is advanced criterion subject matter that I want to cover there, but it doesn't have to be done as written. As part of splitting the projects up, do something with the benchmark section. I am worried though that removing the benchmarking section would make project 4 too small, but worth trying and seeing. Maybe just delete the whole thing, and file an issue to re-add the criterion content, with a link to the commit the deleted the old text.

The advanced parallelism section of project 4 today is very exposition heavy, but ultimately is one big-bang "make it lock-free" step. During a rewrite I would split it into: split readers and writers into two, each with their own lock; remove the lock from the reader.

@brson brson added type/enhancement New feature or request component/rust labels Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant