On 10/04/18 18:11, 赵 俊 wrote: > My Squid with configuration of Icap like this: > > > #icap > icap_enable on > icap_preview_enable on > icap_preview_size 1024 > icap_send_client_ip on > adaptation_meta X-Client-Port "%>p" > icap_206_enable on > icap_persistent_connections off > > > icap_service service_req reqmod_precache 0 icap://192.168.10.200:1344/echo > icap_service service_res respmod_precache 1 icap://192.168.10.200:1344/echo > adaptation_access service_res allow all > adaptation_access service_req allow all > > > When I configured the Icap parameter of Squid , the number of new > connection or the number of concurrent connections was less than half > as only Squid running. > So how to configure Icap can improve the performance of proxy? You cannot improve it much in that aspect. ICAP is a networking protocol for sending HTTP traffic to an external service. It uses ports and network connections to do that. AFAIK the best efficiency it can do is just under x2 the amount a normal Squid uses - every inbound client connection uses +1 REQMOD socket and every outbound server connection adds +1 RESPMOD socket. Even with pipelining/persistence and caching that is not changed. eCAP modules do not use the extra network resources. But whether you can go that way depends on what you are needing it to do. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
