Data Explorer: Request profiles one at a time for larger tables #9096
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are some changes to make profile rendering a little smoother. Before we were batching 4 profiles at a time, but this changes to 1-at-a-time for over 1 million rows (below that they the in-window profiles are requested in a single big batch):
I also noticed that the background task queue in Python was using 5 x # CPUs by default and for compute heavy profile computation this can result in inefficient context switching when computing many profiles. Now the number of workers is equal to the number of logical CPU cores.
Before:
Screen.Recording.2025-08-19.at.16.31.58.mov
After:
Screen.Recording.2025-08-19.at.16.30.45.mov
Release Notes
New Features
Bug Fixes
QA Notes
Check data frames with at least 10 million rows to observe the sparkline pop-in performance.
@:data-explorer