You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: