What problem does your feature solve?
The design approach for integrating the loadtest package internally into a target application's ingestion code path such as demonstrated on #5794 for Horizon and equally applicable in other apps targeted for using loadtest like rpc or galexie introduces some tight coupling between the app and loadtest going forward.
What would you like to see?
- load testing is transparent to the application
- no coupling from application code to loadtest, applications have a net zero-code adjustment to use loadtest.
- analyze an alternative for leveraging the existing go/ingest/loadtest to be packaged as a 'blackbox' cli tool and can be invoked as a substitute in place of the usual captive core bin. Applications set their
CAPTIVE_CORE_BIN=loadtest_tool, the cli tool bin mocks the 'catchup' and 'run' parameter invocations.
What alternatives are there?
Change the application ingestion code path to Integrate with go/ingest/loadtest and establish new app config parameters related to loadtest such as demonstrated here for Horizon.
What problem does your feature solve?
The design approach for integrating the loadtest package internally into a target application's ingestion code path such as demonstrated on #5794 for Horizon and equally applicable in other apps targeted for using loadtest like rpc or galexie introduces some tight coupling between the app and loadtest going forward.
What would you like to see?
CAPTIVE_CORE_BIN=loadtest_tool, the cli tool bin mocks the 'catchup' and 'run' parameter invocations.What alternatives are there?
Change the application ingestion code path to Integrate with go/ingest/loadtest and establish new app config parameters related to loadtest such as demonstrated here for Horizon.