On 2/9/2015 2:16 PM, Baptiste wrote: > A single CPU core (choose the fastest one with AESNI enabled) can > easily handle you current traffic and meet also the requirements of > your capacity planning. > > From a memory point of view, 16G sounds more than enough for your > traffic expectation. > > To get some configuration tips, you can browse > http://fr.slideshare.net/ssl247/webinar-ssl-en from slide 18th for > HAProxy tips (that said, many useful information in the slide before).
For a relatively cheap server option (The Dell PER430, part of Dell's latest server generation), these are the processor choices. I pre-selected the fastest option from a pure clock speed standpoint, at 3Ghz: https://www.dropbox.com/s/fi45xhb85k5p99u/dell-r430-cpu.png?dl=0 The number of cores doesn't really concern me, but I suspect that the amounts of L1, L2, and L3 cache will be important. Can you confirm or deny that suspicion? How important are other CPU factors that may be less obvious, like the bus speed to main memory and things I may not even have considered? There is a more expensive server option (the R730) that has even faster processors with more cache available. The highest clock speed available there is 3.5Ghz. The price premium is high. Naturally I'd like to spend the least money possible, but I don't want to shortchange myself on the amount of SSL capacity I'm getting. With these as choices, any specific recommendations? I'm eyeballing a change from E5-2623 to E5-2630 on the R430 ... the clock speed is significantly lower, but it has twice as much L1/L2/L3 cache. All these processors have AESNI support. I can get earlier server models for far less money, but they would not have the latest processor generations. Do you know how an E5-2407 processor would do compared to the E5-26xx models on the latest generation? http://ark.intel.com/products/75782/Intel-Xeon-Processor-E5-2407-v2-10M-Cache-2_40-GHz Thanks, Shawn
