Performance

Sambar Server Documentation

Performance

The Sambar Server has several performance enhancing features that can be enabled or disabled to suite the needs of your site. This document outlines several performance tuning techniques.

Content Caching
The server provides an internal File cache mechanism which can be used to increase performance dramatically. The config/config.ini parameters affecting the file cache are:

File Cache Size is used to define the total file cache size in bytes.
Maximum Cached File is used to configure the largest file that should be cached.
Cache Stat Interval indicates how often, in seconds, to stat files (see below).
Cache Flush Interval indicates how often, in seconds, the cache should be flushed (once it becomes full).

The System Administration interface provides cache statistics to assist with tuning the cache hit performance. For maximum performance, configure the File Cache Size large enough to serve all files out of memory file cache memory.

The stat cache caches the results of recent stat() system calls. Virtually all web server requests cause the server to stat() at least one file (and often many) depending on the configuration settings. This adversely affects performance and is often unnecessary, as the same files or directories are queried repeatedly and usually return the same status. The stat cache amortizes the cost of these file system operations over many requests and improves performance, at the cost of using more memory and adding delay between the time a file changes and the time the server notices (this period is configurable: Cache Stat Interval).

DNS Caching
The DNS cache caches the results of recent gethostbyname() system calls. The proxy server in particular makes significant use of this call when routing proxy requests. DNS lookups that result from the gethostbyname call can adversely affect system performance. It is recommended that a gethostbyname() interval of 3600 (1 hour) be configured for active proxy servers.

Versioning
When WebDAV is enabled and Content Versioning is used, the .DAV directory includes a compressed (gzip) version of all files stored under the version control system. The server takes advantage of this when returning static pages to clients by returning the compressed file rather than the uncompressed file if the user's browser accepts gzip encodings (IE 4.0+ and Netscape 4.0+). This can significantly improve server performance and speed delivery by reducing the amount of data transfered. Benchmarks indicate an average improvement of 30% for HTML content.

Compress Content
The config/config.ini file contains a boolean parameter Compress Content that, if enabled, instructs the server to compress all dynamic content and content with a mime type of text* being returned from the server if the user's browser accepts gzip encodings (IE 4.0+ and Netscape 4.0+). This feature differs from the Versioning enhancement described above in that real-time gzip compression is performed on dynamic content (content from shtml, stm, servlets, cgi-bin etc.) In general, internet servers or servers delivering content across a WAN should enable content compression; servers utilized for intranets only will see little benefit unless bandwidth is limited. In addition, content compression can be enabled for specific mime types via .htaccess rules.