Help for Performance

If you see a problem with your performance with your server being too slow, it could be related to any of the following:

• Your network speed
• The traffic on your LAN
• The number of clients requesting from your server
• The number of threads set on your server

To change the performance settings

1. Fill in the following fields:
   • Server priority - a priority class for the Internet Connection Secure Server. The operating system uses priority classes to determine which processes have priority over others. Valid values are:
     • 0 - no priority
     • 1 - maximum priority as a normal process
     • 2 - maximum priority as a foreground server process
     You may want to use a value of 0 if the machine your server is running on is also processing other types of requests.
   • Maximum number of active threads - the maximum number of threads that you want to have active at one time. If the maximum is reached, the server holds new requests until another request finishes and threads become available. Generally, the more requests your server receives, and the more power your machine has, the higher the value you should use for this directive.

     Each time your server receives a request from a client, it uses one or two threads to perform the requested action (one thread if the server is not performing DNS lookup, two threads if the server is performing DNS lookup).

   • Check ACL files for file protection - select whether ACL files will be checked for file protection. Set this directive to values of always, never, or protect only for better server performance. With an always value, the server will always look for an ACL file on every file request; with a never value, the server will never look for an ACL file on a file request; and with a protect only value, the server will only look for an ACL file when the file request is for a file that is covered by a protection statement.
   • Use Meta files - select whether the server will use meta files when serving files. Set this directive to off for better server performance.
   • Persistent connection timeout - the amount of time the server should wait between client requests before cancelling a persistent connection. Include the measure of time, such as "seconds" or "minutes" in this field. For example, you could specify 30 seconds or 2 minutes.
   • Maximum number of requests to receive on a persistent connection - the maximum number of requests the server should receive on a persistent connection. When determining this number, be sure to consider the number of images used in your pages. Each image requires a separate request.
2. Click Apply to update your server with the changes you made to the form
   or
   Click Reset to return to the values that were on the form before you made the changes.