vqServer Performance


  • Java servlets, supported by vqServer, are a fast and resource-efficient alternative to CGI scripts and proprietary server APIs.
  • vqServer supports Java servlets in the most efficient way possible. Native-code servers need to instantiate a Java Virtual Machine and invoke a Java servlet engine to support servlets.
  • vqServer supports some functions internally (and therefore efficiently) which would require CGI scripts or server extensions in other environments (for example redirection, user self-registration and custom login pages).

Improving performance

The following measures will improve vqServer's performance. However the effect of many of theses measures will be imperceptible in most situations and some may be impractical.

  • Use Microsoft's JVM or version 1.1.8 of Sun's JVM instead of the latest Java Platform 2.
  • Stop or close all other applications and utilities while vqServer is running.
  • Make the file cache as large as possible without causing disk thrashing (you will need to experiment with vqServer's system settings to do this).
  • Enable persistent HTTP connections (this is the default).
  • Gradually increase the minimum threads and maximum threads settings for the main web server until vqServer stops getting more responsive.
  • Disable logging unless required. This also saves disk space.
  • Make sure that background writing of log files is enabled (this is an option on the system settings page of the control centre).
  • Disable the autosave feature.
  • Disable cache checking (by setting the cache timeout setting of the system settings to -1) if your web pages are infrequently updated.
  • Disable the connection timeout feature.
  • Enable the persistent HTTP connection feature but set the HTTP keep-alive timeout to 0.
  • Use as few servers as possible. Don't create additional servers unless it's really necessary.
  • Switch off unused servers. For example, if you have permanent access to the computer on which vqServer is running, switch off the administration server from the vqServer window when you're not using it (this is also a security measure).
  • Disable the vqServer window's connnections display and the console's connections display.
  • Use as few aliases, users, access control lists and file types as possible (the effect of this measure on performance is so small that it's hard to measure).


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

Contents

Compatibility
Version history