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

GUI Based Analysis is Orders of Magnitude Slower Than CLI #667

Open
gfs opened this issue Nov 1, 2022 · 1 comment
Open

GUI Based Analysis is Orders of Magnitude Slower Than CLI #667

gfs opened this issue Nov 1, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@gfs
Copy link
Contributor

gfs commented Nov 1, 2022

Describe the bug
With a large database (tested with 300+MB) analysis that takes only a few seconds directly with the CLI takes quite a while on the GUI, and there is no real progress notification.

Expected behavior
I think we should add a button to skip writing the analysis results to the database if possible, perhaps storing them in AppState, which is I suspect the bottleneck.

@gfs gfs added bug Something isn't working enhancement New feature or request and removed bug Something isn't working labels Nov 1, 2022
@gfs
Copy link
Contributor Author

gfs commented Nov 3, 2022

further investigation fins this is largely because the methods to write analysis records to the database are not sharded and thus only single threaded. I think its worth exploring two approaches, the one proposed above, and alternatively (or also) changing analysis results to be sharded like collect results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant