perftest-toolkit VS perftest-toolkit

--- # defaults file for profiled-traffic-generator # URI that includes your password and portal endpoint in the following format: ://@. # The can be either the provider key or an access token for the 3scale Account Management API. # is the URL used to log into the admin portal. # Example: https://[email protected] threescale_portal_endpoint: https://@3scale-admin.apps.aucunnin-ccs.lpi0.s1.devshift.org/ # Used traffic for performance testing is not real traffic. # It is synthetically generated traffic based on traffic models. # Information about available traffic profiles (or test plans) can be found here: # https://github.com/3scale/perftest-toolkit/blob/master/buddhi/README.md#profiles # Currently available profiles: [ simple | backend | medium | standard ] traffic_profile: simple # Private Base URL # Make sure your private application behaves like an echo api service # example: https://echo-api.3scale.net:443 private_base_url: https://echo-api-echo-api.apps.aucunnin-ccs.lpi0.s1.devshift.org # Public Base URL # Public address of your API gateway in the production environment. # Optional. When it is left empty, public base url will be the hosted gateway url # example: https://gw.example.com:443 public_base_url:

I was interested in doing some load testing against 3scale. After a bit of digging around I found that there was an open source load testing toolkit in https://github.com/3scale-labs/perftest-toolkit.