Rules are for the good of the group, and timeouts are no exception. Timeouts are configured to fit normal program execution.
When troubleshooting timeout errors, first verify that the timeout is not caused by idle application containers. Sometimes timeouts can be reached when working with inefficient code or when attempting to execute a long-running job that would be better suited for Terminus.
|Maximum time a script can run before being terminated by the parser. This includes Drush & WP-CLI commands. Helps prevent poorly written scripts from tying up your application container's PHP workers.
You can edit this timeout via
wp-config.php. Scripts executed through the GlobalCDN will still be restricted by the 59 second connection timeout.
|Typically reached if you try to index too much at once (use a reasonable batch size and avoid indexing large binary files).
|Number of seconds to wait for a timeout.
|First Byte Timeout
|Number of seconds to wait for the first byte.
|Between Bytes Timeout
|Number of seconds to wait for between bytes.
|Pantheon executed Drupal cron
|Only applies to Pantheon's automatic hourly execution of Drush cron.
|Number of seconds a script can run. If reached, the script returns a fatal error.
|Applies to HTTPS requests and requests to a DNS A record. Requests using the Pantheon CNAME for HTTP requests are not limited.
|10 minutes idle
|Applies to remote Drush and WP-CLI commands, SSH tunneling, SFTP, rsync.
|Number of seconds to wait for a block to be written to a connection before aborting the write.
|Number of seconds to wait for more data from a connection before aborting the read.
|Number of seconds the server waits for activity on a non-interactive connection before closing it.
|Number of seconds the server waits for activity on an interactive connection before closing it.
|PHP won't run forever.
All web requests are set to 59 seconds. Fastly's GCDN terminates the request if the backend does not respond after 59 seconds. PHP will continue to process the request until it hits the PHP
max_execution_time, however the results will not be relayed to the user browser, because the connection has already terminated.
All non-web requests, such as those that do not pass Fastly's CDN, have a maximum timeout of 120 seconds. This includes requests from Terminus or PHP scripts via SSH.
If the request passes through port
443 it will timeout at 59 seconds.
Yes, use the command
terminus drush <site>.<env> -- cron in Terminus. Most slow cron executions are due to PHP errors or a slow external service. Best practice is to identify and fix the root cause. Check log files and review PHP errors and exceptions for clues.
If you're migrating to a Drupal site, you can also configure Migrate to trigger Drush imports from the UI by configuring the
migrate_drush_path variable to:
$conf['migrate_drush_path'] = $_ENV['HOME'] . '/bin/drush';
No, these settings apply to every site on Pantheon. One of the ways Pantheon scales so well is by avoiding one-off configurations. We run a highly tuned universal configuration for optimized performance.
Do not edit the
pantheon_apachesolr module within your Drupal site installation, it will void your warranty and we can't support user modifications. Instead, reduce the batch size and avoid indexing large binary files.
If you receive a
The application did not respond in time error when trying to install a theme or plugin, your experience may be affected by a combination of large files and a poor internet connection. Extract the files locally and upload them via SFTP.
Agencies that frequently deploy sites using a common set of themes and plugins should consider creating a custom upstream.