ballerina-platform / ballerina-performance-cloud
Ballerina Performance Tests in Cloud
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing ballerina-platform/ballerina-performance-cloud in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Repository Overview (README excerpt)
Crawler viewBallerina Container based Performance Tests This repository contains container based performance tests for Ballerina. The tests are running in an AKS cluster. Dashboard https://ballerina.io/ballerina-performance-cloud/ Adopting load tests for standard libraries • All the tests in the standard library should reside inside directory in the repository root. • Create a directory inside for the test. We will call it here. • The test should have four directories inside. • deployment • results • scripts • src • The directory should contain the ballerina package that has to be load tested. This project should have entry inside Ballerina.toml and it should have Cloud.toml file to configure the docker and Kubernetes artifacts. • The directory should contain the additional kubernetes artifacts that should be applied on top of c2c genrated yaml. This will be done using Kustomize. and is mandatory here. You can add any additional yamls you require for the deployment in this directory (helper pods, mysql etc). kustomization.yaml ingress.yaml • The directory is used to hold the scripts required for load test execution. It must contain run.sh file which will be responsible for running the load test. You can include the .jmx file and access it via the directory via $scriptsDir variable in the run.sh file. You can additionally have (ex - to install dependencies for required test) and (ex - to modify results csv) in the same directory. Sample run.sh file • The directory should contain summary.csv file with the following header. Results of the tests will be appended to this file. • When your test is ready, you can commit your test suite for any repository under and execute https://github.com/ballerina-platform/ballerina-performance-cloud/actions/workflows/stdlib_workflow.yml by giving the repository name as an input.