Le 13 janvier 2012 07:29, Eliezer Croitoru <eliezer@xxxxxxxxxxxxxxxxxx> a écrit : > On 12/01/2012 19:58, Gerson Barreiros wrote: >> >> I have an unique server doing this job. My scenario is most the same >> as mentioned above. >> >> I just want to know if i can make this server a Virtual Machine, that >> will use shared hard disk / memory / cpu with another VMs. > > web proxy on a vm is not the best choice in a mass load environment. > you can use on a vm but in most cases it will mean lower performances. > > i have a place with 40Mbps atm line that is using 2 squid servers on a vm > and it works fine. > another one is an ISP with 4 machines with a total of 800Mbps output to the > clients. > > statistics is one of the musts before getting a conclusion. > > Eliezer > This subject is tricky, as many of here has told. Number of user is not a relevant data. You shall state exactly what is "slow Internet" and when that happens to define clearly your problem. How ever, I pas you some tips here: - About machine, more RAM more quicker - Replace default LRU cache policy for mem cache use heap GDSF, and for disk heap LFUDA - If you are using a slow disk (using /dev/hdX instead of /dev/sdX as a rule of dump) please try to void disk cache - place cache_dir tree directory structure (L1 and L2) wider to void FS problmes (ext2 has issues with too many files in a directory) - place a local DNS, - place DNS TTL cache bigger than default. 15 mins is a rsonable value - if using authentication us bigger cache ttl times to void slow negotiation - at ACL configuration, remember there is short-circuit logic so when adding http_access clausles, place in first them acl what higher likehood to fail, this will speed up Dont hesitate on contact me offline LD