Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tools: prepare block-generator for configuring apps #5443

Merged
merged 9 commits into from
Jun 9, 2023
Merged

tools: prepare block-generator for configuring apps #5443

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
33df0b9
cherry pick from apps branch
Jun 2, 2023
516598a
pass blockgen tests
Jun 2, 2023
eb533a4
Update tools/block-generator/generator/config.go
tzaffi Jun 2, 2023
1a962e3
Merge remote-tracking branch 'origin/master' into tools-blockgen-config
Jun 7, 2023
c91b3d0
fix bad merge for consensusTimeMilli
Jun 7, 2023
3f2b194
prepare for apps child PR
Jun 7, 2023
a0dc673
bugfix
Jun 7, 2023
3d13b4f
Merge pull request #18 from tzaffi/purely-reorg
tzaffi Jun 8, 2023
5099dfa
Merge remote-tracking branch 'origin/master' into tools-blockgen-config
Jun 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
43 changes: 33 additions & 10 deletions tools/block-generator/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,19 +10,20 @@ Block generator uses a YAML config file to describe the composition of each rand
2. Transaction type distribution
3. Transaction type specific configuration

At the time of writing, the block generator supports **payment** and **asset** transactions. The settings are hopefully, more or less, obvious. Distributions are specified as fractions of 1.0, and the sum of all options must add up to 1.0.
The block generator supports **payment**, **asset**, and **application** transactions. The settings are hopefully, more or less, obvious. Distributions are specified as fractions of 1.0, and the sum of all options must add up to ~1.0.
shiqizng marked this conversation as resolved.
Show resolved Hide resolved

Here is an example which uses all of the current options. Notice that the synthetic blocks are not required to follow algod limits, in this case the block size is specified as 19999:
Here is an example which uses all of the current options. Notice that the synthetic blocks are not required to follow algod limits, in this case the block size is specified as 99,999:

```yml
name: "Mixed (19,999)"
name: "Mixed (99,999)"
genesis_accounts: 10000
genesis_account_balance: 1000000000000
tx_per_block: 19999
tx_per_block: 99999

# transaction distribution
tx_pay_fraction: 0.3
tx_asset_fraction: 0.7
tx_pay_fraction: 0.5
tx_asset_fraction: 0.3
tx_app_fraction: 0.2

# payment config
pay_acct_create_fraction: 0.02
Expand All @@ -34,6 +35,28 @@ asset_optin_fraction: 0.1
asset_close_fraction: 0.05
asset_xfer_fraction: 0.849
asset_delete_fraction: 0

# app choice config
app_swap_fraction: 0.5
app_boxes_fraction: 0.5

# app_swap config
app_swap_create_fraction: 0.001
app_swap_update_fraction: 0.001
app_swap_delete_fraction: 0
app_swap_optin_fraction: 0.1
app_swap_call_fraction: 0.98
app_swap_close_fraction: 0.005
app_swap_clear_fraction: 0.003
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you please elaborate what you have mind for an app swap scenario? are these apps using the swap opcode?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is out of context. #5450 sheds a bit of light. In particular, I'm creating two apps with teal code:

  1. for populating boxes
  2. for swapping assets using inner transactions

That PR doesn't actually make boxes / swap assets yet, but it does create the apps and set some local state.


# app_boxes config
app_boxes_create_fraction: 0.001
app_boxes_update_fraction: 0.001
app_boxes_delete_fraction: 0
app_boxes_optin_fraction: 0.1
app_boxes_call_fraction: 0.98
app_boxes_close_fraction: 0.005
app_boxes_clear_fraction: 0.003
```

## Modes
Expand Down Expand Up @@ -77,7 +100,7 @@ transaction_pay_total:30024226
transaction_pay_create_total:614242
early_average_import_time_sec:2.13
early_cumulative_import_time_sec:1083.26
early_average_imported_tx_per_block:19999.00
early_average_imported_tx_per_block:99999.00
early_cumulative_imported_tx_per_block:10179491
early_average_block_upload_time_sec:NaN
early_cumulative_block_upload_time_sec:0.00
Expand All @@ -88,7 +111,7 @@ early_overall_transactions_per_second:9397.09
early_uptime_seconds:3600.06
final_average_import_time_sec:2.35
final_cumulative_import_time_sec:3602.62
final_average_imported_tx_per_block:19999.00
final_average_imported_tx_per_block:99999.00
final_cumulative_imported_tx_per_block:30598470
final_average_block_upload_time_sec:NaN
final_cumulative_block_upload_time_sec:0.00
Expand Down Expand Up @@ -143,7 +166,7 @@ A typical **runner** scenario involves:

First you'll need to get a `conduit` binary. For example you can follow the [developer portal's instructions](https://developer.algorand.org/docs/get-details/conduit/GettingStarted/#installation) or run `go build .` inside of the directory `cmd/conduit` after downloading the `conduit` repo.

Assume you've navigated to the `tools/block-generator` directory of
Assume you've navigated to the `tools/block-generator` directory of
the `go-algorand` repo, and:

* saved the conduit binary to `tools/block-generator/conduit`
Expand All @@ -158,4 +181,4 @@ Then you can execute the following command to run the scenario:
### Scenario Report

If all goes well, the run will generate a directory `tmp/OUTPUT_RUN_RUNNER_TEST`
and in that directory you can see the statisticsn of the run in `scenario.report`.
and in that directory you can see the statistics of the run in `scenario.report`.