Re: ATS Sizing

[Trilok Nathreddy <tr...@gmail.com>]

Leif,

We have around 30 k concurrent connections and most of the traffic is
telemetry traffic to upload diagnostic data ( <2KB)

any considerations/best practices you can suggest?

Regards
Trilok

On Mon, Jul 27, 2020 at 9:05 PM Leif Hedstrom <zw...@apache.org> wrote:

>
>
> > On Jul 22, 2020, at 11:24 PM, Trilok Nathreddy <tr...@gmail.com>
> wrote:
> >
> > Need a suggestion on how we can size the specs to deploy apache traffic
> server  on RHEL platforms ( cpu , ram needed) and also how to factor no of
> concurrent connection, do we have any best practices to share too.
>
>
> This is near impossible to answer without knowing your use case / data set
> / load. A raspberry Pi would be fine if you are doing a few hundred
> requests per second.
>
> Cheers,
>
> — Leif
>
>
>

Re: ATS Sizing

[Leif Hedstrom <zw...@apache.org>]

> On Aug 5, 2020, at 6:21 AM, Trilok Nathreddy <tr...@gmail.com> wrote:
> 
> Leif,
> 
> We have around 30 k concurrent connections and most of the traffic is telemetry traffic to upload diagnostic data ( <2KB)
> 
> any considerations/best practices you can suggest?


30k active connections? How many QPS? How many new TLS sessions / sec? Likely, you’ll be CPU bound with such small payloads. Is anything cacheable? If not, obviously you don’t have to consider RAM or disk cache (other than RAM for the connections).

— Leif