What happened?
PR #842 previously addressed a similar problem by experimenting with .load() after merge operations.
Although .load() was later reverted (due to full-run slowdowns), subsequent refactoring or dependency updates (Xarray/Dask/NetCDF4) may have reintroduced similar inefficiencies.
Performance in recent standalone is slower than prior E3SM Diags releases 3.0.0.
What did you expect to happen? Are there are possible answers you came across?
No response
Minimal Complete Verifiable Example (MVCE)
run example/run_all_sets_E3SM_machines.py
only include `arm_diags` set.
Relevant log output
Anything else we need to know?
No response
Environment
v3.1.0
What happened?
PR #842 previously addressed a similar problem by experimenting with .load() after merge operations.
Although .load() was later reverted (due to full-run slowdowns), subsequent refactoring or dependency updates (Xarray/Dask/NetCDF4) may have reintroduced similar inefficiencies.
Performance in recent standalone is slower than prior E3SM Diags releases 3.0.0.
What did you expect to happen? Are there are possible answers you came across?
No response
Minimal Complete Verifiable Example (MVCE)
Relevant log output
Anything else we need to know?
No response
Environment
v3.1.0