RE: Proxy server: Squid + dansguardian



I need setup a proxy server with RHEL5.6_x86-64 + squid +
dansguardian with NTLM auth support.

This server will be used by about 200 users, but this value can be
increased in near future until about 500 users.

Somebody know which HW requeriments should I consider?
Hi,

What's about build this system virtual.
In this case you can change the resources later if you need more.


Squid is quite HDD intensive so I wouldn't virtualize it. It also
benefits from all the memory you can give it.

If you're going to have a lot of rules then CPU should also be taken
into account: high frequency and high QPI.

For starters: get very fast drives (SAS with high RPM) and all the RAM
you can (1333 MHz).

For about 1900 users we have a virtualized squid proxy with NTLM auth running on 2GB of memory and one vCPU. Memory seems to be about right for our environment but we may look at adding a CPU soon.

A quick glance shows it's writing at about 350 KBps. I'm not sure there's a sound argument against virtualizing based on disk throughput anyway, at least in our experience, as the fiber channel storage that serves the virtual clusters performs much better than the direct attached storage the previously non-virtual servers had.

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



Relevant Pages

  • Re: pcib allocation failure
    ... pcib1: attempting to grow prefetch window for ... attempting to grow memory window for ... cpu0: on acpi0 ... <ACPI PCI bus> on pcib0 ...
    (freebsd-current)
  • Next July 27: boot failure(hang) on x86_64 box.
    ... Freeing unused kernel memory: 1360k freed ... ACPI: PM-Timer IO Port: 0x488 ... CPU: L2 Cache: 1024K ... # AX.25 network device drivers ...
    (Linux-Kernel)
  • [PATCH] Document Linuxs memory barriers [try #3]
    ... The attached patch documents the Linux kernel's memory barriers. ... I've tried to get rid of the concept of memory accesses appearing on the bus; ... barring implicit enforcement by the CPU. ...
    (Linux-Kernel)
  • Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
    ... Bios 1.04beta did show correct memory sizing in dmidecode, ... I hope this is as simple as me doing something glaringly wrong in the kernel ... DMI present. ... CPU: L2 cache: 6144K ...
    (Linux-Kernel)
  • Re: read vs. mmap (or io vs. page faults)
    ... not fit in main memory, and there are overheads related to the heuristics ... But because the CPU is underutilized, ... reasonably sized user buffer). ... You have to measure the actual overhead to see what the actual cost is. ...
    (freebsd-questions)