On Tue, Sep 25, 2018 at 10:51 PM Willy Tarreau <w...@1wt.eu> wrote:

Hi Willy,

> Just be careful as you are allocating 64GB of RAM to the TCP stack.

Yeah, after I figured that out I set it down to 1M / 4GB ram which is
enough to handle peak traffic on only one proxy VM.

> As a hint, take a look at the connection timers in your logs.

I calculated some stats from a sample of about 400K requests:

  Tw mean: 0.00 ms
  Tw std dev: 0.00 ms
  Tw max: 0.00 ms
  Tw median: 0.00 ms

  Tt mean: 296.70 ms
  Tt std dev: 4724.12 ms
  Tt max: 570127.00 ms
  Tt median: 1.00 ms

  Tr mean: 22.90 ms
  Tr std dev: 129.48 ms
  Tr max: 19007.00 ms
  Tr median: 1.00 ms

  Tc mean: 0.59 ms
  Tc std dev: 17.49 ms
  Tc max: 1033.00 ms
  Tc median: 0.00 ms

  Tq mean: 0.01 ms
  Tq std dev: 7.90 ms
  Tq max: 4980.00 ms
  Tq median: 0.00 ms

So it looks like Tc isn't the issue here. Everything else looks good
to my eyes. I still think something else changed, because on Jessie
this never happened like I said.

> But I also confess I've not run a VM test myself for a
> while because each time I feel like I'm going to throw up in the middle
> of the test :-/

I know that's always been your position on VMs (ha) but one day I
decided to try it for myself and haven't had a single issue until now.
Our old hardware sat nearly 100% idle most of the time, so it was hard
to justify the expense.

Performance on hardware is much better, I'm sure, but none of my tests
show enough of a performance boost to justify even the $93/mo servers
I was looking at renting. Properly tuned VMs have worked really well
for us.

> We're mostly saying this because everywhere on the net we find copies of
> bad values for this field, resulting in out of memory issues for those
> who blindly copy-paste them.

Yep I totally understand that. I think I was just saying that since
everyone says "never change this" there was no discussion around what
it is exactly, what it does, what happens during memory pressure mode,
how to measure if you need to change it, etc.

> Regards,
> Willy

Thanks for chiming in on this, Willy.

-- 
Brendon Colby
Senior DevOps Engineer
Newgrounds.com

Reply via email to