Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update load-and-performance-testing.md #2249

Closed
wants to merge 1 commit into from
Closed

Update load-and-performance-testing.md #2249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/_docs/load-and-performance-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ You should:

<div class="alert alert-info" role="alert">
<h3 class="info">Note</h3>
<p><strong>Load testing should only be performed on the Live environment</strong>. Dev has much lower default caching settings than other environments to facilitate iterative development. Test has the exact same configuration as Live, but Test can only have one appserver, while Live can have as many as your plan allows. If disruptive behavior occurs outside of the Live environment, the site may be temporarily disabled to prevent disruption to other customers.</p></div>
<p><strong>If you have not launched your site yet, you should perform your load tests on the Live environment</strong>. If your site is already live, you should perform your load tests in the Test environment so that you do not risk downtime on your live site as a result of the load test. When performing your load tests in the Test environment, you should scale down your test traffic to correspond to the number of containers in your live environment, so if you have two app servers in your Live environment and only one app server in your Test environment, reduce the number of users in your load test by 50%. The Dev environment has much lower default caching settings than other environments to facilitate iterative development. Test has the exact same configuration as Live, but Test may only have one appserver, while Live can have as many as your plan allows. If disruptive behavior occurs outside of the Live environment, the site may be temporarily disabled to prevent disruption to other customers.</p></div>

## Performance vs. Scalability

Expand All @@ -29,7 +29,7 @@ High-performance is the ability to deliver a page in under a second; scalability
## Verify Varnish is Working

To verify that the [Varnish](/docs/varnish) cache is working, the `curl` command can be run with the `-I` flag to gather and display header information. Header information can also be obtained via [Firebug](http://en.wikipedia.org/wiki/Firebug_(software)) or [Inspect](http://en.wikipedia.org/wiki/Google_Chrome) in the browser. The results should be something like this:

```nohighlight
curl -I http://live-yoursite.pantheonsite.io
HTTP/1.1 200 OK
Expand All @@ -48,7 +48,7 @@ X-Pantheon-Edge-Server: 108.166.96.132
Vary: Accept-Encoding, Cookie
```
The "Age" field should be greater than 0. If the max age is not greater than 0, please review [Drupal's Performance and Caching Settings](/docs/drupal-cache#drupal-7-performance-configuration) and [Varnish Caching for High Performance](/docs/varnish) documentation.

<div class="alert alert-danger" role="alert">
<h3 class="info">Warning</h3>
<p>Until Varnish has been correctly configured, don't worry about further testing.</p></div>
Expand Down