Improved TCP tuning:
Improved TCP tuning was introduced with SafeSquid version 4.2.0. The SafeSquid executable now allows you to set the socket-timeout in seconds. Increasing the socket timeout will make SafeSquid keep the connection open for a thread. This allows a thread to handle consecutive requests from same source, by reusing the last opened socket. While increasing the SOCKET_TIMEOUT can increase throughput, please remember it can cause SafeSquid to segfault if the kernel closes a socket, that SafeSquid "thinks" is open. You may set SOCKET_TIMEOUT to 1, for maximum application stability, and sacrifice performance. Setting SOCKET_TIMEOUT to approximately 30% of your fin_timeout should be ok for most cases. In any case SOCKET_TIMEOUT should not exceed fin_timeout
Improved Thread tuning:
Improved Thread tuning was introduced with SafeSquid version 4.2.0. The SafeSquid executable now allows you to set the thread timeout (in seconds) when awaiting another connection to handle. This is still an experimental feature, and keeping at 1, should be safest. Increasing this can increase speed, but may also cause random segfaults, if unfortunately the kernel has closed the handle.
Password Caching was introduced with SafeSquid version 4.2.0. Password Caching reduces latency when authentication is desired from a remote authentication system. Password Caching also tremendously reduces the stress on the system's PAM sub-system. You can set Password Cache to "<Password_Cache_Size> :<Password_expiry_time in seconds >". This will automatically define the maximum memory utilised for password caching and the time in seconds, before the authentication will be considered aged, if no matching request is received.