[p4] Perforce server lockup problem

Robert Cowham robert at vaccaperna.co.uk
Tue Mar 8 03:31:19 PST 2005

I know of 2 companies that had problems upgrading to a new box running
Windows 2003 server, though they were both running p4d 2003.2. The culprit
turned out to be anti-virus software.
One other point for you is what version of the p4d server did you upgrade
from and how big are your branches and how much integration history do you
have? The integration behaviour changed in 2004.2 to make it more
intelligent about  finding the common ancestor, but I presume this is at the
cost of having to do more work (I don't know, but am looking forward to the
presentation at the user conference on this subject!). It is *possible* you
are hitting an edge case in this.
It might be worth installing an older version of your p4d (using the
checkpoint before you upgraded) on similar hardware and test things out. If
you don't have suitable hardware, then perhaps you can do it on your new box
if you have enough disk space to duplicate things, and a slack period when
to try.


From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Smith, Jeremy R
Sent: 08 March 2005 07:18
To: Erik Johnson; perforce-user at perforce.com
Subject: RE: [p4] Perforce server lockup problem

I have never seen behavior like this...the closest that we have seen are
database write slowdowns having to do with AntiVirus software.  Are you sure
it's the perforce process that's introducing the disk writes?
I swear by Mark Russinovich's tools at http://www.sysinternals.com to show
what's really happening on the system.
I would also consider checkpointing the database and restoring from the

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com]On Behalf Of Erik Johnson
Sent: Monday, March 07, 2005 12:22 PM
To: perforce-user at perforce.com
Subject: [p4] Perforce server lockup problem

I'll try and give as much data on our setup, along with the problem we've
been having. I haven't gotten any really crisp leads from Perforce support
on this problem. Maybe someone else has already solved it.
We're running our Perforce server on Windows 2003 server on a machine with
2GB RAM, a RAID 5 disk subsystem with 7200RPM SATA drives, and a single
3.GHz HT processor. We're running server version P4D/NTX86/2004.2/73359
Our general workflow (and the one that tends to generate the problem) is
that we have a main branch that few people directly work on, with personal
branches off of it that individual developers integrate into. There are
roughly 20 developers integrating roughly 5,000 lines of code a day.
Unfortunately, we changed a couple of variables at once when the problem
started happening (upgraded server software, server hardware), so I can't
reasonably point to a specific root cause.
When a developer is merging from their personal branch into our main
codeline, we're seeing total database lockup, and constant reads on the
server (viewed via Windows perfmon). This means that all other users on the
system cannot sync, integrate, checkout, checkin, etc. The condition
generally takes around 15 minutes to clear, and then things all go back to
normal. CPU and RAM usage on the system is all nominal, and while the reads
on the disk subsystem are constant, they are not within 1/3 of the observed
peak read throughput.
Has anyone else seen behavior like this? It appears that the database is
being read table by table for some reason.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.perforce.com/pipermail/perforce-user/attachments/20050308/e15e2ae3/attachment-0007.html>

More information about the perforce-user mailing list