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

Don't start ScopeThread's until UI is initialized #231

Closed
azonenberg opened this issue Oct 12, 2020 · 1 comment
Closed

Don't start ScopeThread's until UI is initialized #231

azonenberg opened this issue Oct 12, 2020 · 1 comment
Labels
performance Something is too slow

Comments

@azonenberg
Copy link
Collaborator

With high-latency instruments, there's contention between waveform downloading and all of the initial queries populating instrument settings from cache.

Would be best if the instrument were kept on hold until the GUI had fully loaded.

@azonenberg azonenberg added the performance Something is too slow label Oct 12, 2020
@azonenberg
Copy link
Collaborator Author

ngscopeclient does background loads of stuff as much as possible, so I think we're probably good. Can make tweaks to individual drivers in the future as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Something is too slow
Projects
None yet
Development

No branches or pull requests

1 participant