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

Add benchmark for reading and writing #48

Open
jamadden opened this issue Jul 16, 2019 · 1 comment
Open

Add benchmark for reading and writing #48

jamadden opened this issue Jul 16, 2019 · 1 comment

Comments

@jamadden
Copy link
Member

We have benchmarks that do each and that do one and then the other, but not one where some workers are reading objects and other workers are writing the same objects. This is a test of invalidation processing and whether reads and writes block each other.

@jamadden
Copy link
Member Author

I'm unsure how to write that as a benchmark. The benchmark functions get to return one timing number, but there are two entirely separate kinds of tasks running whose times aren't related. I could spawn threads inside the benchmark function and take an average, or just return the time of the reader.

Maybe the bench_read_after_write is a good enough test of this.

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

No branches or pull requests

1 participant