Date: Sat, 11 Apr 2015 15:19:45 +0000 From: opendaddy@hushmail.com To: "Raimund Sacherer" <rs@logitravel.com> Cc: freebsd-questions@freebsd.org Subject: Re: Initial request to server extremely slow after longer periods of inactivity Message-ID: <20150411151945.B265FA01DE@smtp.hushmail.com> In-Reply-To: <369199529.123430074.1428656504549.JavaMail.zimbra@logitravel.com> References: <20150409034121.7D7C720395@smtp.hushmail.com> <CADqw_gL6b4fYyda9GzKt4BGv=d=sASttf4bp2_W%2B6JnuKQUCjg@mail.gmail.com> <20150409113928.EE31F401E4@smtp.hushmail.com> <CADqw_gK8-bxeNTYw4ATQnSM-w0iNBVWma83hMScdbsCwzEGxEw@mail.gmail.com> <20150409185801.1B1E9401E3@smtp.hushmail.com> <369199529.123430074.1428656504549.JavaMail.zimbra@logitravel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On 10. april 2015 at 9:01 AM, "Raimund Sacherer" <rs@logitravel.com> wrote: > >Then what I would do in your case is open a few ssh sessions, run >top with cpu focus in one, top with IO focus in another and in a >third i would take a tcpdump written to a file. Maybe another >session with vmstat to check on pagin/pageout, etc. > >Then I'd wait the appropriate amount of time and try a web >connection, if it takes long, I'l check the top's if there is >something going on (lot's of CPU, lot's of IO, pages etc.) and >check the tcpdump in wireshark to see if there are problematic DNS >queries which maybe are timing out, etc. Wouldn't SSH sessions act as "continuous feedback loops" preventing the server from going unresponsive in the first place? Also, how can I do stuff like `traceroute` or `mtr` knowing beforehand that the server is indeed unresponsive? Since it's only unresponsive on first requests, if I send a request to check, things will have returned to normal by the time I get to run those commands. Thanks! O.D.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150411151945.B265FA01DE>