Agoric / dapp-orchestration-basics

Agoric Orchestration Sample dApp
2 stars 4 forks source link

e2e-testing / starship configured to use more RAM than necessary #89

Open 0xpatrickdev opened 1 week ago

0xpatrickdev commented 1 week ago

What is the Problem Being Solved?

e2e-testing/config.yaml, modeled from agoric-sdk/multichain-testing/config.yaml, currently requires 10 GB of ram allocated in Docker to start.

This in turn:

The error usually manifests itself as pods in a Pending for a long time, and an "Insufficient memory" error in the kubectl describe pod agoriclocal-genesis-0 output.

However:

Description of the Design

config.yaml without, or with less, resources overrides is tested and checked in for dapp-orchestration-basics.

A minimal goal should be less than < 8GB, so we don't need to adjust Docker settings. It would best to go as low as we can, which might be cpu: "0.2" and memory: "400M" according the starship docs linked above.

CPU should also be considered in this exercise.

We might also consider checking in multiple starship configs, one could just run a single remote chain and relayer instead of two of each.

Test Plan

Manual testing is likely sufficient, but should be verified by multiple parties.

0xpatrickdev commented 1 week ago

The docs should also give guidance on minimum system reqs: