About choosing the right instance type for Varnish in AmazonEC2
Reza Naghibi
reza at varnish-software.com
Fri Mar 10 22:54:15 CET 2017
Just to chime in:
- 1 CPU is a good starting point, as others have said, Varnish does not
need much CPU. If you max out the CPU, then move to 2 CPUs, repeat...
- Do not change any of the thread settings, the defaults will work nice
on a single CPU or more.
--
Reza Naghibi
Varnish Software
On Fri, Mar 10, 2017 at 3:16 PM, Craig Servin <cservin-varnish at cromagnon.com
> wrote:
> We found that we run into the network IO limits before we had CPU issues.
> You have to use trial and error to figure out how much IO you can get from
> each instance type as we couldn't find good documentation defining that.
> However it seemed that the network limit goes up as you step up machine
> sizes in each family.
>
> You could also put your varnish into an ASG and add instances on CPU or
> Network IO. The cache wouldn't be shared between them, but depending on
> your traffic that may not matter.
>
> At our busiest time we were running 6 c4.4xlarge instances 3 east 3 west.
> Now, we run 4 r4.xlarge instances. The nice thing about them being virtual
> is you can load test them and then load test another instance type fairly
> easily.
>
> Cheers,
>
> Craig
>
>
> On 2017-03-10 03:58, Jordi Llach wrote:
>
>> Hi guys,
>> any suggestion choosing an Amazon EC2 instance type for Varnish ?
>>
>
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170310/0e207c4d/attachment.html>
More information about the varnish-misc
mailing list