From: "J.H." <warthog9@kernel.org>
To: David Brown <davidb@codeaurora.org>
Cc: sedat.dilek@gmail.com, LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, ftpadmin@kernel.org,
webmaster@kernel.org
Subject: Re: patchwork.kernel.org down
Date: Mon, 20 Dec 2010 17:00:59 -0800 [thread overview]
Message-ID: <4D0FFC4B.9050301@kernel.org> (raw)
In-Reply-To: <20101220204936.GA21290@huya.qualcomm.com>
On 12/20/2010 12:49 PM, David Brown wrote:
> On Mon, Dec 20, 2010 at 09:12:58PM +0100, Sedat Dilek wrote:
>
>> just FYI: http://patchwork.kernel.org/ is down!
More excitement from https://bugzilla.kernel.org/show_bug.cgi?id=20702
Anyone want to take a stab at it? I know I'd be appreciative. I am
running a debug kernel with everything I could find and enable I even
remotely thought might prove helpful. Nothing has jumped out yet though.
> git.kernel.org seems to be down as well.
git isn't down, but it has been unbelievably busy. Loads are *only* in
the 60's right now (they have been spiking above 300)
I did mention the loads and the spikes yesterday:
https://lkml.org/lkml/2010/12/20/317
and you can see the loads on the odins (the ones that deal with git) here:
http://cacti.kernel.org/graph_view.php?action=tree&tree_id=3
We are down from the 2700 or so simultaneous git processes to only about
1600 right now (which again the normal range is 100-200). The onslaught
is subsiding, as it does with any big release, just no one knew it was
going to be nearly as big as it has turned out to be.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2010-12-21 0:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 20:12 patchwork.kernel.org down Sedat Dilek
2010-12-20 20:49 ` David Brown
2010-12-21 1:00 ` J.H. [this message]
2011-01-05 22:52 ` Roland Dreier
2011-01-05 23:48 ` Randy Dunlap
2011-01-06 2:58 ` Roland Dreier
2011-01-10 18:52 ` Roland Dreier
2011-01-10 20:04 ` J.H.
2011-01-10 20:33 ` Roland Dreier
2011-01-11 0:45 ` J.H.
2011-01-10 20:53 ` Roland Dreier
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=4D0FFC4B.9050301@kernel.org \
--to=warthog9@kernel.org \
--cc=davidb@codeaurora.org \
--cc=ftpadmin@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=webmaster@kernel.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;
as well as URLs for NNTP newsgroup(s).