F-SECURE INTERNET GATEKEEPER WINDOWS 2000-2003 SERVER 6.61 Administrator's Manual page 278

278
Keep the Connection Alive
Scan Result Cache
Threads Per Child Process
If the network has only a few clients and the server load is small, you can
increase Keep alive timeout and Maximum keep alive requests values to
optimize the performance. If F-Secure Internet Gatekeeper has many
clients, the server load increases and Keep alive timeout may need to be
kept shorter, but it should be long enough for browsers to retrieve
complete web pages with all the content.
When the Keep alive timeout is short, connections are closed while users
are reading web pages and opened again when they continue browsing.
For more information, see
Use Scan Result Cache to process frequently accessed web pages
faster. You can increase the Scan result cache size value to store more
scan results in the cache. Using Scan Result Cache does not weaken the
security, as F-Secure Internet Gatekeeper verifies that only exactly the
same files may pass without scanning that have been scanned already.
For more information, see "Performance", 119.
Scan Result Cache is automatically reset every time any settings
are changed, when virus definition databases are updated, and
when the product is restarted.
The Threads per child process setting defines how many clients can use
F-Secure Internet Gatekeeper at the same time. Usually, browsers open
about 4 connections to F-Secure Internet Gatekeeper, so with 50 threads
per child process, F-Secure Internet Gatekeeper can serve up to 12
clients at the same time. Increasing the Threads per child process value
consumes more memory, but makes F-Secure Internet Gatekeeper more
responsive to requests. For more information, see "Performance", 119.
If the child process cannot handle the load with the specified
amount of threads, it creates more threads automatically.
"Network Configuration", 94.