MAINT: Use a large resource class to speed up build

[larsoner]

Interested in trying a large resource class since ERP_CORE_* (e.g. ERN) appears to be CPU-bound with 2 CPUs. First I'm pushing an empty commit just to make sure CIs are green and replicate the ~19 minute timing. Then we'll try a large resource class to see if it helps!

[hoechenberger]

I'd like to ensure we keep the same amount of memory though. These resource limits have helped me discover inefficient memory utilization in the past

[larsoner]

That would be a bit harder. We could run with ulimit maybe. Let's see if the speed gains are there first. Then we can decide if the tradeoff of increased memory limit is worth it.

Actually thinking about it the n_jobs to dask have a fixed limit of 2gb in their config so it should be safe enough in those jobs at least -- and those are the ERP CORE ones that will probably benefit most!

[larsoner]

Okay that did take it from 35 minutes down to 30, which is nice. Looks like all the ERP_CORE got faster, and it should be memory-safe to increase the resource class here since (for parallel at least) we use a memory limit on the dask workers:

no-op commit	resource-class: large

There wasn't much effect for the others (e.g., ds000248) though, so I'll revert those then merge.

[larsoner]

... actually 1810 went from 12 to 8 min which seems worth it, too. So the effect is that just one of the tests (1810) is run no longer as memory limited, which seems worth it