From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: TCP Queuing problem
Date: Wed, 21 Sep 2016 17:30:04 -0700 [thread overview]
Message-ID: <CAN0CFw0v=-i75_b4eNsgMcpJDr2vegsxbsuycR6XHdPvMMy_VA@mail.gmail.com> (raw)
In-Reply-To: <2623549.Xjt69W3Giq@serenity>
>> >> I haven't mentioned it yet, but several times I've seen the website
>> >> perform fine all day until I browse to it myself and then all of a
>> >> sudden it's super slow for me and my third-party monitor. WTF???
>> >
>> > I had a similar problems once when routing through a IPsec VPN tunnnel.
>> > I needed to reduce MTU in front of the tunnel to make it work
>> > correctly. But I think your problem is different.
>>
>> I'm not using IPsec or a VPN.
>>
>> > Does the http server backlog on the other side? Do you have performance
>> > graphs for other parts of the system to see them in relation? Maybe
>> > some router on the path doesn't work as expected.
>>
>> I've attached a graph of http response time, CPU usage, and TCP
>> queueing over the past week. It seems clear from watching top, iotop,
>> and free than my CPU is always the bottleneck on my server.
>
> I'm going to throw one more tool at you; give atop a try. (htop is nice, too,
> but atop is more powerful.)
I think I got it. I'll post all the gory details shortly.
- Grant
next prev parent reply other threads:[~2016-09-22 0:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 21:13 [gentoo-user] TCP Queuing problem Grant
2016-09-19 17:23 ` [gentoo-user] " Grant
2016-09-19 21:25 ` Grant
2016-09-20 0:38 ` Grant
2016-09-20 13:08 ` Grant
2016-09-21 4:01 ` Kai Krakow
2016-09-21 14:30 ` Grant
2016-09-21 19:29 ` Kai Krakow
2016-09-21 19:37 ` Grant
2016-09-21 20:06 ` Kai Krakow
2016-09-21 20:28 ` Kai Krakow
2016-09-21 19:41 ` Kai Krakow
2016-09-21 19:53 ` Grant
2016-09-21 20:18 ` Kai Krakow
2016-09-21 20:47 ` Grant
2016-09-21 21:44 ` Michael Mol
2016-09-22 0:30 ` Grant [this message]
2016-09-22 7:06 ` Kai Krakow
2016-09-25 0:25 ` Grant
2016-10-01 9:57 ` Grant
2016-09-20 13:50 ` J. Roeleveld
2016-09-20 14:53 ` Grant
2016-09-20 18:06 ` J. Roeleveld
2016-09-20 19:52 ` Grant
2016-09-20 20:19 ` Alarig Le Lay
2016-09-22 16:58 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN0CFw0v=-i75_b4eNsgMcpJDr2vegsxbsuycR6XHdPvMMy_VA@mail.gmail.com' \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox