domains / families / science / weather-pipeline-performance-diagnosis
weather-pipeline-performance-diagnosis
authentic
Diagnose slow weather-data workflows by measuring discovery, transfer, parsing, scientific processing, and rendering separately before changing code.
When to use
- A fetch, sounding, map, animation, or batch job feels slower than before.
- A parser or native backend is blamed without stage-level timing evidence.
- Local runs and packaged or hosted runs have different performance.
- A cache, provider fallback, optional enrichment, or rendering step may hide
- A proposed performance fix needs a repeatable before-and-after comparison.
When not to use
- External-service latency and hosted-runner capacity can remain variable even
- Instrumentation has overhead; keep it lightweight and measure coarse stages
- This skill identifies bottlenecks but does not determine whether an expensive
Skill page
Source