Fast USDC load test

[dckc]

What is the Problem Being Solved?

Our tests to date tear down the world after a handful of operations. We don't know the impact on the chain under sustained load.

Description of the Design

Goal: a load test to verify that some metrics don't grow over time: pending kernel promises, number of kernel objects, clist.

cc @mhofman

Security Considerations

Scaling Considerations

kinda the whole point

Test Plan

TBD

Upgrade Considerations

[mhofman]

I will provide a way to get the relevant metrics.

The loadtest should exercise all expected scenario over a sufficient number of iteration to trigger kernel GC. Alternatively if using a bootstrap style test it may be possible to reduce the number of iteration and call reapAllVats on the controller. We're looking at getting the relevant metrics at least before and after the main iteration loop, but should also consider getting them between iterations.

[dckc]

broke ground...

~/projects/agoric-sdk/packages/boot$ yarn test test/fast-usdc/chain-impact.test.ts 
  - [todo] uncompressedSize of heap snapshots of vats
  ✔ access relevant kernel stats after bootstrap
    ℹ relevant kernel stats {
        clistEntries: 2064,
        kernelObjects: 640,
        kernelPromises: 41,
        promiseQueuesLength: 0,
      }
  ─

  1 test passed
  1 test todo
Done in 36.38s.

dc-fu-impact branch:

2025-01-31 15:28 0c8a2d0202 chore: extract relevant kernel stats
2025-01-31 15:19 0abe3bcd3a chore: use local (node) worker for faster dev, initially
2025-01-31 15:16 f6911aaa20 test: Fast USDC chain impact test (WIP)