We see that most of the performance tool uses shared resources and very heavy weight. The performance testing is also used very late in the project lifecycle leading to code changes. The PerTaaS allows us to use resources on demand and can be instrumental in doing the performance test very early while using the shift left approach. Thanks to the API driven approach, it can fit in any CI/CD tool in market. The k8s cronjobs can be use be used to trigger the performance test at scheduled frequency to ensure that there are no surprises when the code changes are pushed. Most of the companies uses performance testing tools running in a specified environment all the time irrespective of whether there are any test running and the cross environment testing introduces unwanted latency and produces incorrect metrics. The k8s environment makes it very easy to run the test for various scenarios like testing a server running in US from a application running in India and see various metrics or running a test which run the performance test from dev to dev region rather than prod to dev region. The running of test on demand makes it easy to schedule resources as they are needed and save cost at the same time.
Log in or sign up for Devpost to join the conversation.