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.
>
>
On Mon, Feb 9, 2015 at 9:50 PM, Shawn Heisey wrote:
> On 2/9/2015 1:08 PM, Baptiste wrote:
>> could you define what you mean by "heavy" ?
>> What type of web application do you host?
>> How many req / conn per second do you expect?
>>
>> When doing SSL, the CPU is not enough, the memory also matte
On 2/9/2015 1:08 PM, Baptiste wrote:
> could you define what you mean by "heavy" ?
> What type of web application do you host?
> How many req / conn per second do you expect?
>
> When doing SSL, the CPU is not enough, the memory also matters.
I would plan on 16 or 32GB of RAM for the machine, mor
On Mon, Feb 9, 2015 at 8:27 PM, Shawn Heisey wrote:
> What should be my goal when buying hardware for haproxy if I am planning
> to secure everything with TLS/SSL terminated by haproxy? Due to
> customer requirements, many of the back-end connections will also be
> encrypted.
>
> Other than getti
What should be my goal when buying hardware for haproxy if I am planning
to secure everything with TLS/SSL terminated by haproxy? Due to
customer requirements, many of the back-end connections will also be
encrypted.
Other than getting the latest processor architecture I can find at the
highest p
5 matches
Mail list logo
