cloudfoundry/routing-perf-release

Name: routing-perf-release

Owner: Cloud Foundry

Description: A BOSH release for routing performance tests

Created: 2015-10-06 18:50:15.0

Updated: 2018-04-11 02:37:15.0

Pushed: 2018-04-11 02:37:14.0

Homepage: null

Size: 13452

Language: Jupyter Notebook

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Routing Performance Release

About

A BOSH release contains tools for running performance tests against the gorouter and TCP router. Gorouter is typically deployed with cf-release and TCP Router with routing-release.

This release will deploy

• throughputramp (c3.large): a BOSH errand responsible for generating load by making requests to gorouter for routes of gostatic. The throughputramp errand will begin by sending 10,000 requests from one thread then linearly scale concurrency to 60 threads, sending 10,000 requests across concurrent threads at each step in the ramp. Latency is recorded for each response and CPU measured periodically throughout the test. Once the test is completed test results are uploaded to S3, from which this report is generated.
• performance_tests: used to run a load test with fixed concurrency against Gorouter or TCP Router
• http_route_populator: responsible for populating gorouter's routing table with routes via the NATS messaging bus. We have most frequently tested with with 1 route or 100,000. Deployment of NATS is a prerequisite.
• tcp_route_populator: responsible for populating the routing table of TCP Router with routes via Routing API. Deployment of Routing API is a prerequisite.
• gostatic (c3.large): the backend app for which http_route_populator registers routes. Gorouter will proxy requests for any of the test routes to the gostatic app, which will return a 200 OK HTTP response with 1024 bytes of data (configurable using gostatic.response_size property).

Get the code

1. Fetch release repo

   r -p ~/workspace
   /workspace
   clone https://github.com/cloudfoundry-incubator/routing-perf-release.git
   outing-perf-release/
   ripts/update
   

2. Automate $GOPATH and $PATH setup

   This BOSH release doubles as a $GOPATH. It will automatically be set up for you if you have direnv installed.

   nv allow
   

   If you do not wish to use direnv, you can simply source the .envrc file in the root of the release repo. You may manually need to update your $GOPATH and $PATH variables as you switch in and out of the directory.

Deploying to BOSH on AWS

Prerequisites

1. Install and start BOSH on AWS.

2. Upload the latest AWS Trusty Go-Agent stemcell to BOSH. You can download it first if you prefer.

    upload stemcell https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-trusty-go_agent
   

3. Make sure you have NATS and gorouter deployed. The http_route_populator job will need gorouter listening on NATS to populate the routing table with routes pointing to the static backend.

4. Make sure you have Routing API and TCP Router deployed. The tcp_route_populator will require the Routing API in order to have TCP routes pointing to the static backend.

   NOTE: The routing_api.auth_disabled property should be set to true since the tcp_route_populator does not support grabbing a UAA token for authentication.

Upload Release, Create a Deployment Manifest, and Deploy

1. Clone this repo; see Get the code.

2. Create and upload the release

   /workspace/routing-perf-release/
   ripts/update
    create release
    -n upload release
   

3. Fill out the cloud-config file and the deployment manifest with the proper values.

4. Update the cloud-config on your director. Beware that support for using v2 manifests on the same director as v1 manifest deployments is supported after BOSH v257.

    update cloud-config manifests/cloud-config-aws.yml
   

5. Deploy the release

    -n -d manifests/perf.yml deploy
   

Deploying to BOSH on BOSH Lite

This assumes you have running CF and Routing Release deployments running on BOSH Lite and that BOSH Lite is updated to a recent version that can support v2 manifest and v1 manifest deployments.

You can follow the above instructions with this cloud-config and deployment manifest Verify that the parameters in the deployment manifest are correct and simply BOSH deploy.

Deploying to BOSH on other IaaS's

If you are deploying this release on any other IaaS's, you can update the cloud-config with the correct cloud_properties. For more information, refer to the BOSH documentation.

Running the load tests

Deploy performance release on your environment. Run the below command

 run errand throughputramp

Errand will upload CPU stats and performance results to an S3 bucket specified in the manifest.

Running Jupyter Notebook for displaying graphs

1. If you have not already done so, download this repo to your local machine.

2. Install Docker locally.

3. Verify the installation by running docker -v.

4. Download CPU stats and performance test files from the S3 bucket specified in the above section. Save these files into the src/jupyter_notebook folder in your local routing-perf-release repo.

5. Rename CPU stats file to cpuStats.csv and performance test file to perfResults.csv. Currently the notebook is configured to look for files with these names. Keep track of what the file names were before to provide a reference point for multiple investigations.

6. Notebook is configured to read metadata file to understand relation between graph and routing release GIT SHA. It currently looks for file with name metadata.yml, with structure

   
    328dhjd
   

7. Run the below command to start the Docker container. Replace PATH_TO_ROUTING_PERF_RELEASE with the actual path to this repo on your local machine. The -v LOCAL_DIR:CONTAINER_DIR command will mount a local directory on your machine to a volume located at CONTAINER_DIR inside this Docker container.

   er run -it -p 8888:8888 -v PATH_TO_ROUTING_PERF_RELEASE/src/jupyter_notebook:/home/jovyan/work jupyter/scipy-notebook
   

8. The docker command will present a token URL that you should copy/paste into a browser to start the notebook session. For example:

   
   9:17:28.023 NotebookApp] The Jupyter Notebook is running at: http://[all ip addresses on your system]:8888/?token=1ce634bd85e4101a74d4114880642381e4f7244af7843093
   9:17:28.023 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
   9:17:28.023 NotebookApp]
   
   opy/paste this URL into your browser when you connect for the first time,
   o login with a token:
      http://localhost:8888/?token=1ce634bd85e4101a74d4114880642381e4f7244af7843093
   

9. Click on the file named Performance_Data.ipynb.

10. Click on the title menu Cell and click on Run All to regenerate the notebook outputs.

11. To compare the current data set with another follow these instructions

12. Add CPU stats and performance results to folder $routing-perf-release-path/src/jupyter_notebook/

13. Rename CPU stats file to old_cpuStats.csv and performance test file to old_perfResults.csv.

14. Go to the Notebook server page and update variable compareDatasets to True and rerun all the cells

15. Add metadata file to with name old_metdata.yml to include GIT sha deatils.

Troubleshooting Jupyter Notebook

1. If you have problem connecting to localhost:8888, you could add the -network=host flag to the above Docker command. You will have to use the IP of the Docker host instead of localhost to connect to the Notebook server. To obtain the IP address of the Docker host, run the command docker-machine ls.