X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7EB72.2D7023AA@onstor-exch02.onstor.net>; Thu, 30 Aug 2007 17:56:42 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7EB72.2D7023AA"
References: <20070830170637.16ca4ccc@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Cron <andys@ripper> cd /home/andy/git; /home/andy/bin/git_rsync.sh
Date: Thu, 30 Aug 2007 17:54:29 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D706@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cron <andys@ripper> cd /home/andy/git; /home/andy/bin/git_rsync.sh
Thread-Index: AcfrYs0lglatNKqURSyXY4Z029ccMwADxDzI
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	<dl-qa>,
	"Kevin Matthews" <kevin.matthews@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7EB72.2D7023AA
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Could it just be that during the day we have such awful random =
performance that things like me running full coverity analyses and =
builds to mightydog shares, coupled with all others doing the =
known-to-be-bad performance of building on NFS trees cause the problem?
=20
I know it shouldn't, but if we have really bad random r/w on small files =
( precisely the case during compilations ) that we uncover a basic =
performance flaw in our software?
=20
-Ken

________________________________

From: Andy Sharp
Sent: Thu 8/30/2007 5:06 PM
To: dl-qa; Kevin Matthews
Subject: Fw: Cron <andys@ripper> cd /home/andy/git; =
/home/andy/bin/git_rsync.sh



Howdy QA & IT folks,

I'm seeing some issues with mightydog that I thought I would run by
y'all to see if anyone can shed some light.

I've been seeing some very poor performance, for a lot of yesterday,
and again I noticed it about 10 minutes ago.  Below is the record of an
rsync from my hard drive to my home directory which started at 4:45.
You can see it took about 9 1/2 minutes for a grand total of about
40KB/sec. That's pretty slow even for a busy filer like mightydog.

Yesterday afternoon, and continuing into the evening, I was modifying
and building a linux kernel repeatedly.  Editing a single file, making
a couple of changes, and then typing 'make', which should take from
15-30 seconds depending if the filer is busy.  Instead I would say the
average time was more than 5 minutes.

Anybody have a clue?  How can I go about finding out what's buggin'
mightydog?

Thanks,

a

Begin forwarded message:

Date: Thu, 30 Aug 2007 16:54:27 -0700
From: andys.sharp@onstor.com (Cron Daemon)
To: andy.sharp@onstor.com
Subject: Cron <andys@ripper>
cd /home/andy/git; /home/andy/bin/git_rsync.sh


Backing up directory /home/andy/git
PING mightydog.onstor.net (10.0.0.222) 56(84) bytes of data.
64 bytes from mightydog.onstor.net (10.0.0.222): icmp_seq=3D1 ttl=3D255
time=3D1.88 ms

--- mightydog.onstor.net ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev =3D 1.880/1.880/1.880/0.000 ms
+ nice -15 rsync -uvHax --delete . /homes/andys/.git
building file list ... done

sent 22122606 bytes  received 20 bytes  39051.41 bytes/sec
total size is 3915591381  speedup is 176.99
+ set +x
Backup to mightydog finished at Thu Aug 30 16:54:27 PDT 2007 with exit
code 0



------_=_NextPart_001_01C7EB72.2D7023AA
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Fw: Cron <andys@ripper> cd /home/andy/git; =
/home/andy/bin/git_rsync.sh</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText33734 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Could it just =
be that during the day we have such awful random performance that things =
like me running full coverity analyses and builds to mightydog shares, =
coupled with all others doing the known-to-be-bad performance of =
building on NFS trees cause the problem?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I know it shouldn't, but if =
we have really bad random r/w on small files ( precisely the case during =
compilations ) that we uncover a basic performance flaw in our =
software?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Ken</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Andy Sharp<BR><B>Sent:</B> Thu =
8/30/2007 5:06 PM<BR><B>To:</B> dl-qa; Kevin Matthews<BR><B>Subject:</B> =
Fw: Cron &lt;andys@ripper&gt; cd /home/andy/git; =
/home/andy/bin/git_rsync.sh<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Howdy QA &amp; IT folks,<BR><BR>I'm seeing some issues =
with mightydog that I thought I would run by<BR>y'all to see if anyone =
can shed some light.<BR><BR>I've been seeing some very poor performance, =
for a lot of yesterday,<BR>and again I noticed it about 10 minutes =
ago.&nbsp; Below is the record of an<BR>rsync from my hard drive to my =
home directory which started at 4:45.<BR>You can see it took about 9 1/2 =
minutes for a grand total of about<BR>40KB/sec. That's pretty slow even =
for a busy filer like mightydog.<BR><BR>Yesterday afternoon, and =
continuing into the evening, I was modifying<BR>and building a linux =
kernel repeatedly.&nbsp; Editing a single file, making<BR>a couple of =
changes, and then typing 'make', which should take from<BR>15-30 seconds =
depending if the filer is busy.&nbsp; Instead I would say the<BR>average =
time was more than 5 minutes.<BR><BR>Anybody have a clue?&nbsp; How can =
I go about finding out what's =
buggin'<BR>mightydog?<BR><BR>Thanks,<BR><BR>a<BR><BR>Begin forwarded =
message:<BR><BR>Date: Thu, 30 Aug 2007 16:54:27 -0700<BR>From: =
andys.sharp@onstor.com (Cron Daemon)<BR>To: =
andy.sharp@onstor.com<BR>Subject: Cron &lt;andys@ripper&gt;<BR>cd =
/home/andy/git; /home/andy/bin/git_rsync.sh<BR><BR><BR>Backing up =
directory /home/andy/git<BR>PING mightydog.onstor.net (10.0.0.222) =
56(84) bytes of data.<BR>64 bytes from mightydog.onstor.net =
(10.0.0.222): icmp_seq=3D1 ttl=3D255<BR>time=3D1.88 ms<BR><BR>--- =
mightydog.onstor.net ping statistics ---<BR>1 packets transmitted, 1 =
received, 0% packet loss, time 0ms<BR>rtt min/avg/max/mdev =3D =
1.880/1.880/1.880/0.000 ms<BR>+ nice -15 rsync -uvHax --delete . =
/homes/andys/.git<BR>building file list ... done<BR><BR>sent 22122606 =
bytes&nbsp; received 20 bytes&nbsp; 39051.41 bytes/sec<BR>total size is =
3915591381&nbsp; speedup is 176.99<BR>+ set +x<BR>Backup to mightydog =
finished at Thu Aug 30 16:54:27 PDT 2007 with exit<BR>code =
0<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C7EB72.2D7023AA--
