AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<dl-software>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
FMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04EC2DDF3@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 8 Dec 2006 14:35:52 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: dl-software
Subject: Fw: Perforce slow again -- BUSTED!
Message-ID: <20061208143552.2bf26cd3@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.5.6 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="MP_5P3tOu3ssb0=v=6kCgB3Lnv"

--MP_5P3tOu3ssb0=v=6kCgB3Lnv
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



Begin forwarded message:

Date: Fri, 8 Dec 2006 14:29:47 -0800
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>
Cc: "Andy Sharp" <andy.sharp@onstor.com>
Subject: Re: Perforce slow again


Kill it! Kill it now! :)

Thanks Larry, now we just have to track down who and what is causing
that. I already caught RonB doing forced p4 syncs of the the whole
depot. This could be the artifact of his earlier attempt.

-Ken

 

-----Original Message-----
From: Larry Scheer
To: Ken Renshaw
CC: Andy Sharp
Sent: Fri Dec 08 14:15:26 2006
Subject: Perforce slow again

Ken,
     Liszt has a p4d at 85% of memory and rising.

Perforce access from clients is beyond slow just now.

What was the solution to unsticking p4d?
Larry

--MP_5P3tOu3ssb0=v=6kCgB3Lnv
Content-Type: text/html; name=.
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>Re: Perforce slow again</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=2>Kill it! Kill it now! :)<BR>
<BR>
Thanks Larry, now we just have to track down who and what is causing that. I already caught RonB doing forced p4 syncs of the the whole depot. This could be the artifact of his earlier attempt.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Larry Scheer<BR>
To: Ken Renshaw<BR>
CC: Andy Sharp<BR>
Sent: Fri Dec 08 14:15:26 2006<BR>
Subject: Perforce slow again<BR>
<BR>
Ken,<BR>
&nbsp;&nbsp;&nbsp;&nbsp; Liszt has a p4d at 85% of memory and rising.<BR>
<BR>
Perforce access from clients is beyond slow just now.<BR>
<BR>
What was the solution to unsticking p4d?<BR>
Larry<BR>
</FONT>
</P>

</BODY>
</HTML>
--MP_5P3tOu3ssb0=v=6kCgB3Lnv--
