Check performance

Once the code has settled, look at the performance, perhaps at several different resolutions. All inline activities (on the critical path) must run in the time that it takes the model to run so that we don't end up with a backlog of data on disk.

No files, tests, or entry points are named. Inspect the inline activities on the critical path and measure them at several resolutions against the climate model runtime; the work is done when they complete within that runtime without creating a data backlog on disk.

Written by the indexing model from the issue text.