Conversation
ninabarbakadze
requested review from
cmwaters,
evan-forbes,
rach-id and
rootulp
as code owners
|
|
||
| For production-like testing on cloud infrastructure: | ||
|
|
||
| TBD |
| talis genesis -s 256 -b ./build | ||
|
|
||
| # Deploy the network (specify SSH key if needed) | ||
| talis deploy --direct-payload-upload --workers 20 |
There was a problem hiding this comment.
probably worth noting the s3 option for faster deployment
There was a problem hiding this comment.
Yes I was going to add that but thought I'd keep everything to minimum. Will add.
Co-authored-by: CHAMI Rachid <chamirachid1@gmail.com>
|
|
||
| 1. **Verify block time configuration for 32MB/3sec blocks:** | ||
|
|
||
| Make sure app is configured for the target throughput. Verify that `DelayedPrecommitTimeout` is set to 2800ms for 3s block time. |
There was a problem hiding this comment.
Where do I verify this? In a file? In a CLI command?
| # Create a .env file | ||
| talis init-env --provider googlecloud | ||
|
|
||
| # Fill in the .env file with your credentials: | ||
| GOOGLE_CLOUD_PROJECT="fibreda" | ||
| GOOGLE_CLOUD_KEY_JSON_PATH="/path/to/service-account-key.json" |
There was a problem hiding this comment.
@tty47 is there a different Google Cloud project that we should use for collecting KPIs? Or is it safe to use the "fibreda" Google Cloud Project?
Note: some of the KPIs aren't related to FibreDA
|
|
||
| ```bash | ||
| talis reset | ||
| talis deploy -w 20 |
There was a problem hiding this comment.
[extreme nit] not worth changing but for future reference I think when commands are in documentation (like this) we should strive to use the long format flag instead of short form flag.
Motivation: as a reader, I don't know what -w controls. But it would make more sense if this said something like:
talis deploy --workers 20
Co-authored-by: Rootul P <rootulp@gmail.com>
3 participants
Overview
Fixes #6591