-
Notifications
You must be signed in to change notification settings - Fork 35
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
R/W ops can get out of sync #140
Comments
As mentioned in Slack, generating the complete workload upfront and distributing these across long-lived threads feels a good idea and would simplify the code and runtime complexity. My only concern is how we would generate the input parameters for the short reads which are currently fed by the results of complex reads at runtime. |
Relevant section from the docs: |
AFAIK the idea behind the pool of complex read results being used to fed short reads is to simulate the behavior of running some complex queries then exploring the area around/looking up the results. |
Moving a discussion on Slack here:
The text was updated successfully, but these errors were encountered: