Optimize list datasets info

[brimoor]

No description provided.

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -0.01% ⚠️

Comparison is base (435c0c1) 15.85% compared to head (ac474d8) 15.84%.
Report is 3 commits behind head on release/v0.22.0.

Additional details and impacted files

@@                 Coverage Diff                 @@
##           release/v0.22.0    #3528      +/-   ##
===================================================
- Coverage            15.85%   15.84%   -0.01%     
===================================================
  Files                  593      593              
  Lines                72763    72768       +5     
  Branches               861      861              
===================================================
  Hits                 11533    11533              
- Misses               61230    61235       +5     

Flag	Coverage Δ
app	15.84% <0.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
...core/src/plugins/SchemaIO/components/ErrorView.tsx	0.00% <0.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[swheaton]

This is a lot faster especially in Teams through API. Was basically unusable before.
Do you think anyone relies on / would miss the num_samples part of the info?

[brimoor]

@swheaton yeah not sure if anyone is relying on num_samples, but there'd be no way to get this information efficiently because it would require n API calls to get estimated counts, and the n API calls part is why the method was slow.

[swheaton]

Right. A little better than loading every dataset completely (which is like n * 4 db calls), but still not ideal.

[swheaton]

lgtm. tested and works well also