|
|
| Rails Default Settings |
| Default configuration for Ruby on Rails applications configured through
Rails Contexts.
|
| |
| Table of Contents |
|
| |
| Ruby Path |  |
|
| Description: Specifies path to 'ruby' executable. Generally it is /usr/bin/ruby
or /usr/local/bin/ruby depending on where ruby has been installed to.
|
| Syntax: Absolute path. |
|
| Rails Environment | |
|
| Description: Specifies which mode Rails will be running as, 'Development' or
'Production'. Default is 'Production'.
|
| Syntax: Select from drop down list |
|
| Max Connections | |
|
| Description: Specifies the maximum concurrent connections that can be established
between the web server and an external application. This setting controls how
many requests can be processed concurrently by an external application.
However, the real limit also depends on the external application itself.
Set this value higher will not help if the external application is not fast enough
or cannot scale to large number of concurrent requests.
|
| Syntax: Integer number |
| Tips: [Performance] Setting a high value does not directly translate to higher performance.
Set the limit to a value that will not overload the the external
application will provide the best performance/throughput. |
|
| Environment | |
|
| Description: Specifies some extra environment variables for the external application.
|
| Syntax: key=value multiple variables can be separated by "ENTER" |
|
| Initial Request Timeout | |
|
| Description: Specifies the maximum time the web server waits for the external
application to respond to the first request over a new established connection.
If the web server does not receive any data from the external application
within this timeout limit, it will mark this connection as bad. This
helps to identify communication problem with external application as
quickly as possible. If some requests take longer time to
process, increase this limit to avoid "503" error messages.
|
| Syntax: Integer number |
|
| Retry Timeout | |
|
| Description: Specifies the period of time that the web server waits before
retrying the external application that had prior communication problem.
|
| Syntax: Integer number |
|
| Keep Alive Timeout | |
|
| Description: Specifies the maximum time to keep an idle persistent connection
open. When set to -1, the connection never timeout. When set to >=0,
the connection will be closed after the timeout has been reached.
|
| Syntax: int |
|
| Response Buffering | |
|
| Description: Specifies whether to buffer response received from external
applications. If Apache's Non-Parsed-Header mode is available enabled, buffering is turned off for response with full HTTP headers.
|
| Syntax: Select from drop down list |
|
| Max Idle Time | |
|
| Description: Specifies the maximum idle time before an external application
is stopped by the server. When set to -1, the external application
will not be stopped by the server. Default value is -1. This feature
allows resources used by idle applications to be freed. It is
especially useful in mass hosting environment when you need to define
many applications running in setuid mode for the sake of maximum
security.
|
| Syntax: Select from radio box |
|
| Back Log | |
|
| Description: Specifies the backlog of the listening socket. Required if Auto Start is enabled.
|
| Syntax: Integer number |
|
| Run On Start Up | |
|
| Description: Specifies whether to start the external application at server start
up. Only applicable to external applications that can manage its own child processes and where 'Instances' value is set to '1'.
If enabled, external processes will be created at server startup instead of run-time.
|
| Syntax: Select from radio box |
| Tips: [Performance] If configured external process has significant startup overhead, such as Rail apps, then
this option should be enabled to decrease first-page response time. |
|
| Priority | |
|
| Description: Specifies priority of the external application process. Value ranges from
-20 to 20, lower number means higher priority. This
priority cannot be set higher (lower number) than server's own. Otherwise, server's
priority will be used and this value is disregarded.
|
| Syntax: int |
| See Also: Server Priority |
|
| Memory Soft Limit | |
|
| Description: Specifies memory consumption limit in bytes for an external application process
or an external application started by server.
The main purpose of this limit is to prevent excessive memory usage
because of software bug or intention attacks, not to impose a limit on
normal usage, make sure to leave enough head room, otherwise your
application will fail and 503 error may be returned. It can be set at server
level or at
individual external application level. Server level limit will be used if
it is not set at individual application level.
Operating system's default will be used if the value is set to
0 or absent at both levels.
|
| Syntax: Integer number |
| Tips: [Attention] Do not over tune this limit, it may result in 503 errors
if your application need more memory. |
|
| Memory Hard Limit | |
|
| Description: same as Memory Soft Limit, "Soft Limit" can be raised up to the
"Hard Limit" from within a user process. It can be set at server
level or at
individual external application level. Server level limit will be used if
it is not set at individual application level.
Operating system's default will be used if the value is set to
0 or absent at both levels.
|
| Syntax: Integer number |
|
| Process Soft Limit | |
|
Description: Limits the total number of processes can be created on behalf
of a user.
This effectively limits the number of processes can be launched by
web server on behalf of a user. All existing processes will be counted
against this limit, not just new process to be started.
If the limit is set to 10, and there are more than 10 processes
running under one user, then no new process can be started by web
server for that user (suEXEC).
The main purpose of this limit is to prevent "fork bomb"
attacks or excessive usage, not to impose a limit on normal usage,
make sure to leave enough head room. It can be set at server level or at
individual external application level. Server level limit will be used if
it is not set at individual application level. Operating system's
default value will be used if this value is 0 or absent at
both levels.
|
| Syntax: Integer number |
|
| Process Hard Limit | |
|
| Description: Same as Process Soft Limit, "Soft Limit" can be raised up to the
"Hard Limit" from within a user process. It can be set at server level or at
individual external application level. Server level limit will be used if
it is not set at individual application level.
Operating system's default value will be used if the value is set to
0 or absent at both levels.
|
| Syntax: Integer number |
|
| |
|
|
| |
Copyright © 2003-2007. Lite Speed Technologies Inc.
All rights reserved. |