From 2ab77cf35a24e70d8fb3a798f055027de7a7bb1a Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Mon, 24 Jun 2019 11:20:57 -0500 Subject: [PATCH 1/6] Added TTFB_TESTED_PAGES --- .../v2.1/cloud/env/variables-post-deploy.md | 42 ++++++-- guides/v2.1/cloud/live/stage-prod-test.md | 32 +++--- .../v2.2/cloud/env/variables-post-deploy.md | 100 +++++++++++++++++- 3 files changed, 151 insertions(+), 23 deletions(-) mode change 120000 => 100644 guides/v2.2/cloud/env/variables-post-deploy.md diff --git a/guides/v2.1/cloud/env/variables-post-deploy.md b/guides/v2.1/cloud/env/variables-post-deploy.md index 3fb17594e60..2d80a59ee84 100644 --- a/guides/v2.1/cloud/env/variables-post-deploy.md +++ b/guides/v2.1/cloud/env/variables-post-deploy.md @@ -15,14 +15,39 @@ stage: {% include cloud/customize-build-deploy.md %} +### `TTFB_TESTED_PAGES` + +- **Default**— `[]` (an empty array) +- **Version**—Magento 2.1.4 and later + +Configure _Time To First Byte_ (TTFB) testing for specified pages to test your {{ site.data.var.ece }} site performance. For each page to test, specify the path or the HTTP or HTTPS URL. + +```yaml +stage: + post-deploy: + TTFB_TESTED_PAGES: + - "index.php" + - "index.php/customer/account/create" + - "https://example.com/catalog/some-category" +``` + +After you specify the pages to test and commit your changes, the _Time To First Byte_ test runs during the post-deploy phase and posts results for each path to the cloud log: + +```terminal +[2019-06-20 20:42:22] INFO: TTFB test result: 0.313s {"url":"https://staging-tkyicst-xkmwgjkwmwfuk.us-4.magentosite.cloud/customer/account/create","status":200} +[2019-06-20 20:42:22] INFO: TTFB test result: 0.408s {"url":"https://staging-tkyicst-xkmwgjkwmwfuk.us-4.magentosite.cloud/checkout/cart","status":200} +``` + +For redirected paths, the log reports the path of the redirect target instead of the one configured in the environment variable. If you specify an invalid path, the log displays a warning message. + ### `WARM_UP_PAGES` -- **Default**— `index.php` -- **Version**—Magento 2.1.4 and later +- **Default**— `index.php` +- **Version**—Magento 2.1.4 and later Customize the list of pages used to preload the cache in the `post_deploy` stage. You must configure the post-deploy hook. See the [hooks section][] of the `.magento.app.yaml` file. -- **single pages**—Specify a single page to add to the cache. You do not have to indicate the default base URL. The following example caches the `BASE_URL/index.php` page: +- **single pages**—Specify a single page to add to the cache. You do not have to indicate the default base URL. The following example caches the `BASE_URL/index.php` page: ```yaml stage: @@ -31,7 +56,7 @@ Customize the list of pages used to preload the cache in the `post_deploy` stage - "index.php" ``` -- **multiple domains**—List multiple URLs. The following example caches pages from two domains: +- **multiple domains**—List multiple URLs. The following example caches pages from two domains: ```yaml stage: @@ -47,11 +72,12 @@ Customize the list of pages used to preload the cache in the `post_deploy` stage :: ``` - - `entity_type`: Choose `category` or `cms-page` - - `pattern|url`: Use a `regexp` pattern or an exact match `url` to filter the URLs, or use an asterisk (\*) for all pages - - `store_id|store_code`: Use the ID or Code of the store or an asterisk (\*) for all stores + - `entity_type`: Choose `category` or `cms-page` + - `pattern|url`: Use a `regexp` pattern or an exact match `url` to filter the URLs, or use an asterisk (\*) for all pages + - `store_id|store_code`: Use the ID or Code of the store or an asterisk (\*) for all stores + + The following example caches these items: - The following example caches: - all category pages for store with ID 1 - category page `cars` for store with code `store_en` - cms page `contact` for all stores diff --git a/guides/v2.1/cloud/live/stage-prod-test.md b/guides/v2.1/cloud/live/stage-prod-test.md index d3207755257..3123f8b1579 100644 --- a/guides/v2.1/cloud/live/stage-prod-test.md +++ b/guides/v2.1/cloud/live/stage-prod-test.md @@ -12,6 +12,7 @@ functional_areas: --- #### Previous step: + [Migrate data and static files]({{ page.baseurl }}/cloud/live/stage-prod-migrate.html) When your code, files, and data is successfully migrated to Staging or Production, use the environment URLs to test your site(s) and store(s). For a list of your URLs, see [Starter]({{ page.baseurl }}/cloud/live/stage-prod-migrate-prereq.html#starter-urls) and [Pro]({{ page.baseurl }}/cloud/live/stage-prod-migrate-prereq.html#pro-urls) access information. @@ -49,7 +50,9 @@ The following examples use Pro URLs. You can use any URL with the `dig` command. Next, use a `curl` command to verify X-Magento-Tags exist and additional header information. The format for the command is: - curl http[s]:// -H "host: " -k -vo /dev/null -HFastly-Debug:1 +```bash +curl http[s]:// -H "host: " -k -vo /dev/null -HFastly-Debug:1 +``` For Starter, enter the full site URL from your environment [Access info]({{ page.baseurl }}/cloud/live/stage-prod-migrate-prereq.html#starter-urls) in the command to view the headers. @@ -58,20 +61,20 @@ For Pro Staging and Production, the command differs per server: * Staging: `curl http[s]://staging..c..ent.magento.cloud -H "host: " -k -vo /dev/null -HFastly-Debug:1` * Production: - * The load balancer: `curl http[s]://.c..ent.magento.cloud -H "host: " -k -vo /dev/null -HFastly-Debug:1` - * A direct Origin node: `curl http[s]://.{1|2|3}..ent.magento.cloud -H "host: " -k -vo /dev/null -HFastly-Debug:1` + * The load balancer: `curl http[s]://.c..ent.magento.cloud -H "host: " -k -vo /dev/null -HFastly-Debug:1` + * A direct Origin node: `curl http[s]://.{1|2|3}..ent.magento.cloud -H "host: " -k -vo /dev/null -HFastly-Debug:1` After you are live, you can also check your live site: `curl https:// -k -vo /dev/null -HFastly-Debug:1`. You can also add `--resolve` if your live URL is not set up with DNS. Check the returned response headers and values: -* `Fastly-Magento-VCL-Uploaded` should be present -* `X-Magento-Tags` should be returned -* `Fastly-Module-Enabled` should be either `Yes` or the Fastly extension version number -* `X-Cache` should be either `HIT` or `HIT, HIT` -* `x-cache-hits` should be 1,1 -* [`Cache-Control: max-age`](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9) should be greater than 0 -* [`Pragma`](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.32) should be `cache` +* `Fastly-Magento-VCL-Uploaded` should be present +* `X-Magento-Tags` should be returned +* `Fastly-Module-Enabled` should be either `Yes` or the Fastly extension version number +* `X-Cache` should be either `HIT` or `HIT, HIT` +* `x-cache-hits` should be 1,1 +* [`Cache-Control: max-age`](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9) should be greater than 0 +* [`Pragma`](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.32) should be `cache` To verify Fastly is enabled in Staging and Production, check the configuration in the Magento Admin for each environment: @@ -209,11 +212,12 @@ We recommend that you review the [Magento Performance Toolkit]({{ site.mage2blob For best results, we recommend the following tools: -* [Siege](https://www.joedog.org/siege-home/): Traffic shaping and testing software to push your store to the limit. Hit your site with a configurable number of simulated clients. Siege supports basic authentication, cookies, HTTP, HTTPS and FTP protocols. -* [Jmeter](http://jmeter.apache.org/): Excellent load testing to help gauge performance for spiked traffic, like for flash sales. Create custom tests to run against your site. +* [Magento application performance test]({{ page.baseurl }}/cloud/env/variables-post-deploy#ttfb_tested_pages)—Test Magento application performance by configuring the TTFB_TESTED_PAGES envrionment variable to test site response time. +* [Siege](https://www.joedog.org/siege-home/)—Traffic shaping and testing software to push your store to the limit. Hit your site with a configurable number of simulated clients. Siege supports basic authentication, cookies, HTTP, HTTPS and FTP protocols. +* [Jmeter](http://jmeter.apache.org/)—Excellent load testing to help gauge performance for spiked traffic, like for flash sales. Create custom tests to run against your site. * New Relic (provided): Helps locate processes and areas of the site causing slow performance with tracked time spent per action like transmitting data, queries, Redis, and so on. -* [Blackfire]({{ page.baseurl }}/cloud/project/project-integrate-blackfire.html) (provided): Helps track through the issues New Relic finds and helps you dig deeper into the issue for specifics. Blackfire profiles the environment and helps locate bottlenecks indepth: process, method call, query, load, and so on. -* [WebPageTest](https://www.webpagetest.org/) and [Pingdom](https://www.pingdom.com/): Real-time analysis of your site pages load time with different origin locations. Pingdom may cost a fee. WebPageTest is a free tool. +* [Blackfire]({{ page.baseurl }}/cloud/project/project-integrate-blackfire.html) (provided)x— Helps track through the issues New Relic finds and helps you dig deeper into the issue for specifics. Blackfire profiles the environment and helps locate bottlenecks indepth: process, method call, query, load, and so on. +* [WebPageTest](https://www.webpagetest.org/) and [Pingdom](https://www.pingdom.com/)— Real-time analysis of your site pages load time with different origin locations. Pingdom may cost a fee. WebPageTest is a free tool. ## Set up Magento Security Scan Tool {#security-scan} diff --git a/guides/v2.2/cloud/env/variables-post-deploy.md b/guides/v2.2/cloud/env/variables-post-deploy.md deleted file mode 120000 index eb8802adce5..00000000000 --- a/guides/v2.2/cloud/env/variables-post-deploy.md +++ /dev/null @@ -1 +0,0 @@ -../../../v2.1/cloud/env/variables-post-deploy.md \ No newline at end of file diff --git a/guides/v2.2/cloud/env/variables-post-deploy.md b/guides/v2.2/cloud/env/variables-post-deploy.md new file mode 100644 index 00000000000..7e932e69403 --- /dev/null +++ b/guides/v2.2/cloud/env/variables-post-deploy.md @@ -0,0 +1,99 @@ +--- +group: cloud-guide +title: Post-deploy variables +functional_areas: + - Cloud + - Configuration +--- +The following _post\_deploy_ variables control actions in the post-deploy phase and can inherit and override values from the [Global variables]({{ page.baseurl }}/cloud/env/variables-global.html). Insert these variables in the `post-deploy` stage of the `.magento.env.yaml` file: + +```yaml +stage: + post-deploy: + POST-DEPLOY_VARIABLE_NAME: value +``` + +{% include cloud/customize-build-deploy.md %} + +### `TTFB_TESTED_PAGES` + +- **Default**— `[]` (an empty array) +- **Version**—Magento 2.1.4 and later + +Configure _Time To First Byte_ (TTFB) testing for specified pages to test your {{ site.data.var.ece }} site performance. For each page to test, specify the path or the HTTP or HTTPS URL. + +```yaml +stage: + post-deploy: + TTFB_TESTED_PAGES: + - "index.php" + - "index.php/customer/account/create" + - "https://example.com/catalog/some-category" +``` + +After you specify the pages to test and commit your changes, the _Time To First Byte_ test runs during the post-deploy phase and posts results for each path to the cloud log: + +```terminal +[2019-06-20 20:42:22] INFO: TTFB test result: 0.313s {"url":"https://staging-tkyicst-xkmwgjkwmwfuk.us-4.magentosite.cloud/customer/account/create","status":200} +[2019-06-20 20:42:22] INFO: TTFB test result: 0.408s {"url":"https://staging-tkyicst-xkmwgjkwmwfuk.us-4.magentosite.cloud/checkout/cart","status":200} +``` + +For redirected paths, the log reports the path of the redirect target instead of the one configured in the environment variable. If you specify an invalid path, the log displays a warning message. + +### `WARM_UP_PAGES` + +- **Default**— `index.php` +- **Version**—Magento 2.1.4 and later + +Customize the list of pages used to preload the cache in the `post_deploy` stage. You must configure the post-deploy hook. See the [hooks section][] of the `.magento.app.yaml` file. + +- **single pages**—Specify a single page to add to the cache. You do not have to indicate the default base URL. The following example caches the `BASE_URL/index.php` page: + + ```yaml + stage: + post-deploy: + WARM_UP_PAGES: + - "index.php" + ``` + +- **multiple domains**—List multiple URLs. The following example caches pages from two domains: + + ```yaml + stage: + post-deploy: + WARM_UP_PAGES: + - 'http://example1.com/test' + - 'http://example2.com/test' + ``` + +- **multiple pages**—Use the following format to cache multiple pages according to a specific regular expression pattern: + + ```terminal + :: + ``` + + - `entity_type`: Choose `category` or `cms-page` + - `pattern|url`: Use a `regexp` pattern or an exact match `url` to filter the URLs, or use an asterisk (\*) for all pages + - `store_id|store_code`: Use the ID or Code of the store or an asterisk (\*) for all stores + + The following example caches: + - all category pages for store with ID 1 + - category page `cars` for store with code `store_en` + - cms page `contact` for all stores + - any category page that contains `car_` and ends with `html` for store with ID 2 + - any category page that contains `tires_` for store with code `store_gb` + + ```yaml + stage: + post-deploy: + WARM_UP_PAGES: + - "category:*:1" + - "category:cars:store_en" + - "cms-page:contact:* + - "category:|car_.*?\\.html$|:2" + - "category:|tires_.*|:store_gb" + ``` + +[hooks section]: {{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#hooks +[CMS]: https://glossary.magento.com/cms/ +[Content elements]: https://docs.magento.com/m2/ce/user_guide/cms/content-elements.html \ No newline at end of file From d39ddbb2e684a89a0f6e29ca00fba90bcca7ec96 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Mon, 24 Jun 2019 11:54:18 -0500 Subject: [PATCH 2/6] Fixed broken link. --- guides/v2.1/cloud/live/stage-prod-test.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/v2.1/cloud/live/stage-prod-test.md b/guides/v2.1/cloud/live/stage-prod-test.md index 3123f8b1579..6f50829318b 100644 --- a/guides/v2.1/cloud/live/stage-prod-test.md +++ b/guides/v2.1/cloud/live/stage-prod-test.md @@ -212,7 +212,7 @@ We recommend that you review the [Magento Performance Toolkit]({{ site.mage2blob For best results, we recommend the following tools: -* [Magento application performance test]({{ page.baseurl }}/cloud/env/variables-post-deploy#ttfb_tested_pages)—Test Magento application performance by configuring the TTFB_TESTED_PAGES envrionment variable to test site response time. +* [Magento application performance test]({{ page.baseurl }}/cloud/env/variables-post-deploy.html#ttfb_tested_pages)—Test Magento application performance by configuring the TTFB_TESTED_PAGES envrionment variable to test site response time. * [Siege](https://www.joedog.org/siege-home/)—Traffic shaping and testing software to push your store to the limit. Hit your site with a configurable number of simulated clients. Siege supports basic authentication, cookies, HTTP, HTTPS and FTP protocols. * [Jmeter](http://jmeter.apache.org/)—Excellent load testing to help gauge performance for spiked traffic, like for flash sales. Create custom tests to run against your site. * New Relic (provided): Helps locate processes and areas of the site causing slow performance with tracked time spent per action like transmitting data, queries, Redis, and so on. From d59a6bc8730569e64bc067e17c2eab35ec8d19e1 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Mon, 24 Jun 2019 14:10:19 -0500 Subject: [PATCH 3/6] Updated based on review feedback --- guides/v2.1/cloud/env/variables-post-deploy.md | 2 +- guides/v2.1/cloud/live/stage-prod-test.md | 2 +- guides/v2.2/cloud/env/variables-post-deploy.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/guides/v2.1/cloud/env/variables-post-deploy.md b/guides/v2.1/cloud/env/variables-post-deploy.md index 2d80a59ee84..5dbc40de9a6 100644 --- a/guides/v2.1/cloud/env/variables-post-deploy.md +++ b/guides/v2.1/cloud/env/variables-post-deploy.md @@ -20,7 +20,7 @@ stage: - **Default**— `[]` (an empty array) - **Version**—Magento 2.1.4 and later -Configure _Time To First Byte_ (TTFB) testing for specified pages to test your {{ site.data.var.ece }} site performance. For each page to test, specify the path or the HTTP or HTTPS URL. +Configure _Time To First Byte_ (TTFB) testing for specified pages to test your {{ site.data.var.ece }} site performance. For each page to page to test, specify the absolute path reference or an absolute URL with protocol and host. ```yaml stage: diff --git a/guides/v2.1/cloud/live/stage-prod-test.md b/guides/v2.1/cloud/live/stage-prod-test.md index 6f50829318b..0e142b3920d 100644 --- a/guides/v2.1/cloud/live/stage-prod-test.md +++ b/guides/v2.1/cloud/live/stage-prod-test.md @@ -212,7 +212,7 @@ We recommend that you review the [Magento Performance Toolkit]({{ site.mage2blob For best results, we recommend the following tools: -* [Magento application performance test]({{ page.baseurl }}/cloud/env/variables-post-deploy.html#ttfb_tested_pages)—Test Magento application performance by configuring the TTFB_TESTED_PAGES envrionment variable to test site response time. +* [Magento application performance test]({{ page.baseurl }}/cloud/env/variables-post-deploy.html#ttfb_tested_pages)—Test Magento application performance by configuring the `TTFB_TESTED_PAGES` environment variable to test site response time. * [Siege](https://www.joedog.org/siege-home/)—Traffic shaping and testing software to push your store to the limit. Hit your site with a configurable number of simulated clients. Siege supports basic authentication, cookies, HTTP, HTTPS and FTP protocols. * [Jmeter](http://jmeter.apache.org/)—Excellent load testing to help gauge performance for spiked traffic, like for flash sales. Create custom tests to run against your site. * New Relic (provided): Helps locate processes and areas of the site causing slow performance with tracked time spent per action like transmitting data, queries, Redis, and so on. diff --git a/guides/v2.2/cloud/env/variables-post-deploy.md b/guides/v2.2/cloud/env/variables-post-deploy.md index 7e932e69403..1ec0ca15cea 100644 --- a/guides/v2.2/cloud/env/variables-post-deploy.md +++ b/guides/v2.2/cloud/env/variables-post-deploy.md @@ -20,7 +20,7 @@ stage: - **Default**— `[]` (an empty array) - **Version**—Magento 2.1.4 and later -Configure _Time To First Byte_ (TTFB) testing for specified pages to test your {{ site.data.var.ece }} site performance. For each page to test, specify the path or the HTTP or HTTPS URL. +Configure _Time To First Byte_ (TTFB) testing for specified pages to test your {{ site.data.var.ece }} site performance. For each page to page to test, specify the absolute path reference or an absolute URL with protocol and host. ```yaml stage: From c311ee094236685802aea41df7d11269a32e0d07 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Mon, 24 Jun 2019 14:31:01 -0500 Subject: [PATCH 4/6] Added release note to ece-tools v2.1 and 2.2 --- guides/v2.1/cloud/release-notes/cloud-tools.md | 2 ++ guides/v2.2/cloud/release-notes/cloud-tools.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/guides/v2.1/cloud/release-notes/cloud-tools.md b/guides/v2.1/cloud/release-notes/cloud-tools.md index c6288b0fc36..bb1f7f3291c 100644 --- a/guides/v2.1/cloud/release-notes/cloud-tools.md +++ b/guides/v2.1/cloud/release-notes/cloud-tools.md @@ -26,6 +26,8 @@ The release notes include: - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content. - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). + + - {:.new}Added the **TTFB_TESTED_PAGES** post-deploy variable to configure _Time to First Byte_ page tests to check Magento Commerce application performance for sites deployed to Cloud infrastructure. See the variable description in [post-deploy variables]({{ page.baseurl }}/cloud/env/variables-post-deploy.html). - {:.fix}Added the `pub/static/.htaccess` file to the exclude list. [Fix submitted by Björn Kraus of PHOENIX MEDIA GmbH](https://github.com/magento/ece-tools/pull/455). diff --git a/guides/v2.2/cloud/release-notes/cloud-tools.md b/guides/v2.2/cloud/release-notes/cloud-tools.md index 153519cf137..89cdca169cd 100644 --- a/guides/v2.2/cloud/release-notes/cloud-tools.md +++ b/guides/v2.2/cloud/release-notes/cloud-tools.md @@ -27,6 +27,8 @@ The release notes include: - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). + - {:.new}Added the **TTFB_TESTED_PAGES** post-deploy variable to configure _Time to First Byte_ page tests to check Magento Commerce application performance on sites deployed to Cloud infrastructure. See the variable description in [post-deploy variables]({{ page.baseurl }}/cloud/env/variables-post-deploy.html). + - {:.fix}Added the `pub/static/.htaccess` file to the exclude list. [Fix submitted by Björn Kraus of PHOENIX MEDIA GmbH](https://github.com/magento/ece-tools/pull/455). - {:.fix}Fixed an error when all validation messages were showing as `Critical` if at least one critical level validator returned an error. From 9fe0b2454be59cf05d330cd5c90d4b98fee42275 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Mon, 24 Jun 2019 20:16:27 -0500 Subject: [PATCH 5/6] Apply suggestions from code review Co-Authored-By: hguthrie --- guides/v2.1/cloud/env/variables-post-deploy.md | 6 +++--- guides/v2.1/cloud/live/stage-prod-test.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/guides/v2.1/cloud/env/variables-post-deploy.md b/guides/v2.1/cloud/env/variables-post-deploy.md index 5dbc40de9a6..84b1d506a0b 100644 --- a/guides/v2.1/cloud/env/variables-post-deploy.md +++ b/guides/v2.1/cloud/env/variables-post-deploy.md @@ -20,7 +20,7 @@ stage: - **Default**— `[]` (an empty array) - **Version**—Magento 2.1.4 and later -Configure _Time To First Byte_ (TTFB) testing for specified pages to test your {{ site.data.var.ece }} site performance. For each page to page to test, specify the absolute path reference or an absolute URL with protocol and host. +Configure _Time To First Byte_ (TTFB) testing for specified pages to test your {{ site.data.var.ece }} site performance. Specify an absolute path reference, or URL with protocol and host, for each page that requires the test. ```yaml stage: @@ -37,7 +37,7 @@ After you specify the pages to test and commit your changes, the _Time To First [2019-06-20 20:42:22] INFO: TTFB test result: 0.313s {"url":"https://staging-tkyicst-xkmwgjkwmwfuk.us-4.magentosite.cloud/customer/account/create","status":200} [2019-06-20 20:42:22] INFO: TTFB test result: 0.408s {"url":"https://staging-tkyicst-xkmwgjkwmwfuk.us-4.magentosite.cloud/checkout/cart","status":200} ``` - +{: .no-copy} For redirected paths, the log reports the path of the redirect target instead of the one configured in the environment variable. If you specify an invalid path, the log displays a warning message. ### `WARM_UP_PAGES` @@ -97,4 +97,4 @@ Customize the list of pages used to preload the cache in the `post_deploy` stage [hooks section]: {{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#hooks [CMS]: https://glossary.magento.com/cms/ -[Content elements]: https://docs.magento.com/m2/ce/user_guide/cms/content-elements.html \ No newline at end of file +[Content elements]: https://docs.magento.com/m2/ce/user_guide/cms/content-elements.html diff --git a/guides/v2.1/cloud/live/stage-prod-test.md b/guides/v2.1/cloud/live/stage-prod-test.md index 0e142b3920d..9be584129f3 100644 --- a/guides/v2.1/cloud/live/stage-prod-test.md +++ b/guides/v2.1/cloud/live/stage-prod-test.md @@ -215,9 +215,9 @@ For best results, we recommend the following tools: * [Magento application performance test]({{ page.baseurl }}/cloud/env/variables-post-deploy.html#ttfb_tested_pages)—Test Magento application performance by configuring the `TTFB_TESTED_PAGES` environment variable to test site response time. * [Siege](https://www.joedog.org/siege-home/)—Traffic shaping and testing software to push your store to the limit. Hit your site with a configurable number of simulated clients. Siege supports basic authentication, cookies, HTTP, HTTPS and FTP protocols. * [Jmeter](http://jmeter.apache.org/)—Excellent load testing to help gauge performance for spiked traffic, like for flash sales. Create custom tests to run against your site. -* New Relic (provided): Helps locate processes and areas of the site causing slow performance with tracked time spent per action like transmitting data, queries, Redis, and so on. -* [Blackfire]({{ page.baseurl }}/cloud/project/project-integrate-blackfire.html) (provided)x— Helps track through the issues New Relic finds and helps you dig deeper into the issue for specifics. Blackfire profiles the environment and helps locate bottlenecks indepth: process, method call, query, load, and so on. -* [WebPageTest](https://www.webpagetest.org/) and [Pingdom](https://www.pingdom.com/)— Real-time analysis of your site pages load time with different origin locations. Pingdom may cost a fee. WebPageTest is a free tool. +* New Relic (provided)—Helps locate processes and areas of the site causing slow performance with tracked time spent per action like transmitting data, queries, Redis, and so on. +* [Blackfire]({{ page.baseurl }}/cloud/project/project-integrate-blackfire.html) (provided)— Helps track through the issues New Relic finds and helps you dig deeper into the issue for specifics. Blackfire profiles the environment and helps locate bottlenecks indepth: process, method call, query, load, and so on. +* [WebPageTest](https://www.webpagetest.org/) and [Pingdom](https://www.pingdom.com/)—Real-time analysis of your site pages load time with different origin locations. Pingdom may require a fee. WebPageTest is a free tool. ## Set up Magento Security Scan Tool {#security-scan} From 772026c829fe64c38a81f130ea026be1e3b87674 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Mon, 24 Jun 2019 19:11:42 -0700 Subject: [PATCH 6/6] Added 2.3 release note for TTFB_TESTED_PAGES --- guides/v2.3/cloud/release-notes/cloud-tools.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guides/v2.3/cloud/release-notes/cloud-tools.md b/guides/v2.3/cloud/release-notes/cloud-tools.md index 2580f337291..11558c2f76b 100644 --- a/guides/v2.3/cloud/release-notes/cloud-tools.md +++ b/guides/v2.3/cloud/release-notes/cloud-tools.md @@ -26,6 +26,8 @@ The release notes include: - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{page.baseurl}}/cloud/env/variables-deploy.html#force_update_urls) content. - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). + + - {:.new}Added the **TTFB_TESTED_PAGES** post-deploy variable to configure _Time to First Byte_ page tests to check Magento Commerce application performance on sites deployed to Cloud infrastructure. See the variable description in [post-deploy variables]({{ page.baseurl }}/cloud/env/variables-post-deploy.html). - {:.fix}Added the `pub/static/.htaccess` file to the exclude list. [Fix submitted by Björn Kraus of PHOENIX MEDIA GmbH](https://github.com/magento/ece-tools/pull/455).