vqServer System settings


System settings form

This form is displayed when you click on System settings in the control centre menu. The form allows you to view and change some settings which are shared by your entire vqServer installation.

Computer name

Also known as the host name, this is one of the pieces of information which computers connected to the Internet use to identify themselves to each other. vqServer provides this information to Java servlets and CGI scripts (so that they can identify your computer to other computers accessing your web site). vqServer tries to figure this information out for itself during its startup sequence. However, there are some circumstances in which vqServer might not be able to do this or might do this incorrectly.

IP address

This is the other piece of information which computers connected to the internet use to identify themselves to each other. See Computer name above.

Check name and IP address at startup

If this box is checked, vqServer attempts to determine your computer's name and IP address from the operating system during its startup sequence. If vqServer can't do this correctly you'll need to set these parameters manually and clear this check box. The box is checked by default.

Check name and IP address now

If this box is checked, vqServer attempts to determine your computer's name and IP address from the operating system when the Ok button in clicked and then redisplays the system settings form. This box is not checked by default.

Maximum size of cache (kb)

vqServer keeps a copy of the files which are most frequently requested from your web site in your computer's memory (this is called the file cache). This results in faster operation. In general, a larger cache means a faster web site. However if the cache is too big your computer will probably start using virtual memory and thrashing its hard disk. The default value of 4024 kb works well.

Maximum size of files in cache (kb)

Most web pages are relatively small, so the best trade-off between total cache size and server efficiency is achieved by restricting the caching mechanism to a large number of small files. The default value of 6 kb means that most web pages will be cached.
Cache timeout (seconds) The interval after which a cache entry is regarded as stale. Stale entries are checked against your computer's file system when requested and updated if necessary. A small value (like the default of 2 seconds) can make a big difference to server performance under heavy loads. A value of zero forces vqServer to check the file system during every request. A negative value disables checking altogether.

Maximum number of active servlets

vqServer also maintains a cache of the most recently used Java servlets, avoiding the overhead associated with initialising and destroying servlets unnecessarily. The default value, 10, is probably enough to cache all of the servlets in use on most small and medium web sites.
HTTP transaction timeout (seconds) The maximum duration of an HTTP transaction between a web browser and vqServer. If a transaction exceeds this duration it will be interrupted and closed. This feature can prevent most web browsers, network problems, operating system bugs and errant Java servlets or CGI scripts from gradually bringing your web site to a halt. The default value, 300 seconds, accommodates all but the most long-winded servlets. A value of zero disables transaction duration checking.
Keep-alive timeout (seconds) Controls vqServer's support for persistent HTTP connections (HTTP keep-alives). The interval is the maximum time vqServer will maintain a TCP/IP connection with a browser between HTTP transactions (provided the browser supports this feature). The default value, 300 seconds, accommodates most browsing behaviour. A value of zero disables keep-alive duration checking. A value of -1 disables keep-alive support.

Autosave interval (seconds)

vqServer automatically saves its configuration file after this interval if any changes have been made. If the interval is zero, the configuration file is saved every time a change is made using the control centre. A negative value disables the autosave feature.

The vqServer configuration file can also be saved manually by clicking on the Other link and then the Save settings link in the control centre menu. The configuration file is also saved automatically when you shut down vqServer.

Write log files in background

If this box is checked, vqServer stores log file entries in memory until it is not busy doing something else before writing them to disk. This has a noticeable effect on vqServer's performance under heavy load.


vqServer version 1.9. Copyright © 1997-2000 Steve Shering and vqSoft. Last updated 22 November 1999.
vqServer
FAQs
Register (free!)
Support

Contents

Sessions
Special security