[p4] HELP!!!

[Jeff Grills]

You may not have done anything wrong.  Restoring from a checkpoint can
reduce DB file sizes, and in doing so it can also improve performance of
your server as well.  I'm surprised that perforce support wouldn't have had
you try rebalancing before moving the files.  And by the way, if you weren't
changing system architectures, you could have just copied your DB files
instead of restoring from the checkpoint.  The bad news is that you've
changed two variables at one time, so it's going to be difficult to know
whether the local files or the DB rebalancing caused any performance changes
you notice.

See http://tinyurl.com/y7r69e or
http://www.perforce.com/perforce/doc.061/manuals/p4sag/07_perftune.html#1055
420 for details about "checkpoints for database tree rebalancing".

j

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Venters, Cheryl
Sent: Sunday, October 22, 2006 1:00 AM
To: perforce-user at perforce.com
Subject: [p4] HELP!!!


We've been having terrible trouble with performance lately and one of the
things Perforce asked us to do is move our db files to the local drive as
opposed to the san. So, when I did that tonight, I checkpointed my original
server and then restored the checkpoint in the new location. I did a
comparison of the two directories and noticed that many of the db files are
about half the size of what they were prior to the restore. Is this expected
behavior? One thing that sent me into a minor panic was that I restored the
checkpoint without a corresponding journal file but that should be okay
since I just checkpointed and there would have been no activity between the
checkpoint and the restore, right?

 

Thanks.

Cheryl