I have a co-worker that is concerned with the idea of moving SSL termination to haproxy, rather than using LVS to NAT the SSL to back end servers directly. It would be handled by one machine, with corosync/pacemaker providing responsive failover to a redundant host.
Below is the CPU info from one of those hosts (a Dell PowerEdge R200). Our websites are not being hit with an enormous traffic load. They stay busy, but we're definitely not Google or CNN. At what traffic level would I need to be concerned about whether the load balancer can handle SSL termination? Hundreds of requests per second? Thousands? You can assume that we will be disabling SSL on the back end. If I need to gather some info (like openssl benchmarks), just me know what command to run. [root@lb1 ~]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 22 model name : Intel(R) Celeron(R) CPU 430 @ 1.80GHz stepping : 1 cpu MHz : 1800.067 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm syscall nx lm constant_tsc up pni monitor ds_cpl tm2 cx16 xtpr lahf_lm bogomips : 3602.87 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: Thanks, Shawn
