development branches
fio
feature/BD-4245-fio-develop-12132022
fio.test
feature/BD-4245-fiotest-develop-12142022
fio.devtools
feature/BD-4245-fiodevtools-develop-12142022
PRs
fio.devtools
https://github.com/fioprotocol/fio.devtools/pull/69
fio
https://github.com/fioprotocol/fio/pull/366
fio.test
https://github.com/fioprotocol/fio.test/pull/328
instructions.
pulll all branches,
build and install fio repo.
start the chain.
run the fio.test branch this will load the chain with 21k domains (the public private keys and account name of the account receiving the domains is printed at the top of the tests, use the pub key in get_fio_domains testing once the chain is set up.
desired tests --
run a full set of regression tests, verify these run.
load the chain with the 21k domains.
then run a script that constantly calls get_fio_domains, while doing this run a regression
we will see if the overhead of the 21k domains causes failures in regression tests.
Integrated testing on 3 node private test net
Ed will set up on the following AWS server
ssh -i "DapixWestPair2.pem" ubuntu@ec2-18-237-87-177.us-west-2.compute.amazonaws.com
Ed will complete the above testing and also will explore various mods to the timeout for secondary index queries on the API node.
results will be capture here as they occur.
environment setup and establishment of regression tests is ongoing.
tactics
I started by re-establishing tests to load the domains with “toooo many domains per fio address”.
I then removed the time constraint on get table rows in the chain plugin.
I then ran tests to see how this version performs.
1) first look to see how the domains performs (get_fio_domains).
2) look at how regression tests perform.
0 Comments