Using Serverless Artillery 40 requests with cache /users/{userId}/tasks (NO PR)

[Pabriones]

Using Serverless Artillery 40 requests with cache /users/{userId}/tasks (NO PR)

[Pabriones]

Date	Activity	Time
03/20/2021	Asking questions from other teams and other research	2.5 hours
03/22/2021	Running test and documenting result	2.5 hours

[Pabriones]

Instruction using Serverless Artillery 40 request with cache for /users/{userId}/tasks

Turning on Cache

• Log in to Azure Portal
• Select Resource Groups > nsg-rg-dev-usw2-tuesday > ASP-nscrgdevusw2tuesday-95ea
• Then on the left hand side under Setting select app then click on nsc-func-dev-usw2-tuesday
• Then on the left hand side under Settings select Configuration then select CACHE-TOGGLE to toggle cache on and off

Once the cache is turned on, you are ready for testing 🤘

Running Test

1. Setup AWS credentials

• Create an AWS user, grab your credentials from a script, tool, and add them to the environment.

In Linux

$ export AWS_ACCESS_KEY_ID=<access-key-id>
$ export AWS_SECRET_ACCESS_KEY=<secret-access-key>
$ export AWS_SESSION_TOKEN=<session-token>

In windows

$ set AWS_ACCESS_KEY_ID=<access-key-id>
$ set AWS_SECRET_ACCESS_KEY=<secret-access-key>
$ set AWS_SESSION_TOKEN=<session-token>

• Run npm install -g serverless and npm install -g serverless-artillery to make sure serverless artillery is properly installed in your local machine

2. Create custom deployment assets

• Create a local copy of the deployment assets for your customization and then deployment to AWS, using the following command slsart configure
• add region information to the serverless.yml file, for example region=us-west-2

3. Deploy

• Go to the folder in your local directory containing script.yml file
• In the command line, run slsart deploy --stage <your-unique-stage-name>
• You can go to your AWS account console > CloudFormation, and see AWS stack - created there depending on the customizations explained in the steps above.

4. Invoke

• run slsart invoke --stage <your-unique-stage-name>
• If you go to AWS Lambda console > find the loadGenerator Lambda corresponding to your stack > Monitoring tab > Invocations graph, you will see that the Lambda function was invoked to generate the load. You can also see the logs produced by the Lambda in CloudWatch Logs.

5. Remove

• The following command will remove the AWS CloudFormation Stack deployed in step 3. slsart remove --stage <your-unique-stage-name>