All of
 help / color / mirror / Atom feed
From: "J.H." <>
Cc: Sedat Dilek <>,
	Stephen Rothwell <>,, LKML <>,
Subject: Re: linux-next: Tree for December 20
Date: Mon, 20 Dec 2010 10:29:44 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12/20/2010 04:12 AM, Sedat Dilek wrote:
> On Mon, Dec 20, 2010 at 1:00 PM, Stephen Rothwell <> wrote:
>> Hi,
>> On Mon, 20 Dec 2010 12:46:08 +0100 Sedat Dilek <> wrote:
>>>> [The mirroring on is running slowly]
>>> Indeed, you know what's wrong with the mirrors?
>> I don't know what is wrong.  The mirroring just seems to be much slower
>> in the last week or so.  Today, it was just over three hours from when I
>> uploaded linux-next until it was mirrored out.
>> I have cc'd the admins.
> Thanks.

Gingerbread released last week, loads have been spiking to well above
300 on the frontend machines, RAM usage has been in the ~20G range (on
machines with 16G of RAM), and we've been running an *AVERAGE* of 2000+
simultaneous GIT processes worldwide (normal is in the 100-200 range).

Bonus points that we blew a drive on one of the machines yesterday.

I don't think anyone was quite expecting the onslaught we have gotten
this time around, and I'm going to have to make some changes before the
next big release (mainly shifting Android over to the bigger machines)

>>> Can you upload the diff-patch (patch-v2.6.37-rc6-next-20101220) to [1]
>>> from your local-tree or place it somewhere else?
>> I cannot upload directly to, I up load to the same place
>> on and the mirroring system puts it on
> I could download the diff-patch.
> $ wget

Running a quick set of stats against the logs we keep from the syncing
I'm seeing:

	All of December:
	Number of cycles: 5848
	Total amount of time spent syncing: 1544407sec
	Average Sync times: 264sec
	Longest time: 24011sec
	Shortest time: 42sec

	Last 10 days:
	Number of cycles: 2144
	Total amount of time spent syncing: 845762sec
	Average Sync times: 394sec
	Longest time: 24011sec
	Shortest time: 45sec

With cyclical patterns of fast and slow syncs.  We seem to be (right
now) in the middle of one of the slow cycles with the last few syncs
taking a couple of hours each.  The culprit, for at least the current
sync, seems to be the box with the highest load and the blown drive,
which I'm also reluctant to disable since it's still handling it's fair
share of the load and dumping all of that onto the opposite US mirror
would not be good either.

- John 'Warthog9' Hawley

  reply	other threads:[~2010-12-20 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 11:46 linux-next: Tree for December 20 Sedat Dilek
2010-12-20 12:00 ` Stephen Rothwell
2010-12-20 12:12   ` Sedat Dilek
2010-12-20 18:29     ` J.H. [this message]
2010-12-20 20:47       ` Stephen Rothwell
2010-12-20 18:34   ` Chris Ball
  -- strict thread matches above, loose matches on Subject: below --
2010-12-20  9:00 Stephen Rothwell
2010-12-20 16:14 ` Zimny Lech
2010-12-20 20:49   ` Stephen Rothwell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.