test(world): add module gas reports for setting many keys

[yonadaa]

Tests setting 10, 100, 1000, 10000 records with KeysInTable and KeysWithValue.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
mud-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 11, 2023 11:30am
mud-example-minimal-react	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 11, 2023 11:30am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 865adc9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[alvrs]

unclear to me atm why the gas report step fails in the checks but work locally

[alvrs]

alright seems like setting 10k keys was too much for the CI

[alvrs]

Unfortunately this change increases the time for the Build and validate artifacts action from 5 minutes to 10 minutes (see https://github.com/latticexyz/mud/actions/runs/5294523734/jobs/9583964860 for comparison), which unfortunately is not a good tradeoff for adding these gas reports.

Because of that I'll close this PR for now, but we can look at it for reference when optimizing the KeysInTable / KeysWithValue modules.

We should also find a way to run these gas reports more efficiently, the Build and validate artifacts is already the slowest action without this change.

[holic]

We should also find a way to run these gas reports more efficiently, the Build and validate artifacts is already the slowest action without this change.

Looks like gas reports are the bulk of this:

I'm hoping we can soon move over to Vulcan gas reports (or pull in the same strategy) once they land, which will mean the gas reports and tests are run at the same time: nomoixyz/vulcan#104