[squid-users] Are there benefits increasing read_ahead_gap in reverse proxy with collapsed_forwarding?

Is there any benefit to changing the read_ahead_gap when running squid as a
reverse proxy?

I'm running squid as a reverse proxy pointing at several origin servers. The
average filesize is 300 MB.

From the documentation, I gather that the default read_ahead_gap 16 kb would
keep the connection from squid to the origin server open for the duration of
the client request.

If I increase the read_ahead_gap to 500 MB, will squid slurp up the entire
file in one read from the origin server?

Also, does the file stay in memory as it's being sent to the client or is it
written to the squid cache? i.e. do I need to worry about memory?

Here's part of the configs:

maximum_object_size_in_memory 100 MB
collapsed_forwarding on
http_port 80 accel defaultsite=origin.example.com
read_ahead_gap 500 MB

I'm running: 2.7.STABLE2 on RHEL5.2 64bit

Thanks,

Charlie
Received on Mon Mar 23 2009 - 22:09:01 MDT