[p4] Perforce performance halts during large file copy

Brad Holt brad.holt at autodesk.com
Thu Nov 9 14:49:56 PST 2006

It can make all the difference for IO just making sure that the
different streams of traffic get shunted off into their own channels.
Whenever I set up a new server now, I make sure to have the metadata,
versioned files, journal, and swap file off in their own IO channels.
This meant giving them all their own volumes, and upgrading the SCSI
disk IO card on the server to be able to accommodate.  Also, I would
steer clear of RAID 5 for the metadata (and probably journal) volume as
the parity calculations on those large db files can bog things down.

Still, if you are not seeing the IO being topped out, then perhaps it is
just a network bandwidth issue?  When your Perforce "...grinds to a
halt..." what resources seem to be topping out - IO, memory, processor,
network reads/writes?  Maybe next time it's struggling, try running some
metadata queries locally from the console and see how performance is.
That should help narrow down the network vs. IO issue if you cannot pull
this information from task manager or performance monitor.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff Desharnais
Sent: Thursday, November 09, 2006 10:25 AM
To: perforce-user at perforce.com
Subject: [p4] Perforce performance halts during large file copy

We are running Perforce 2005.2 on a Windows Server 2003.

We are having problems where the Perforce server grinds to halt when
someone is copying a large set of files to the machine that runs the
perforce server... Even though the files are being copied to a different
drive than Perforce's.

Recent scenario:

User begins copying 18gigs of data to a drive on the server.

Perforce appears to hang up completely and everyone loses access to the

We restart the service and it runs okay for a few mintues. Shortly
after, Perforce becomes very slow and eventually grinds to a halt again.

The file copy is canceled and things are now running fine again.

Can anyone explain why this may be happening? I don't see the system
being hogged by I/O yet Perforce still seems to grind to a halt during
network I/O activity. This also happened when a user tried using Winrar
to extract files that live on the server. Same results - Perforce grinds
to a halt.

Any ideas?


Jeff Desharnais
IT Specialist
Mad Doc Software
100 Burtt Rd., Suite 220
Andover, MA  01810
(978) 409-6272 Ext. 132

perforce-user mailing list  -  perforce-user at perforce.com

More information about the perforce-user mailing list