Doh. Somehow I sent this way too soon.
We have 266 clients for 117 users, which isn't too bad considering many people
have clients on both windows and linux platforms. I don't think we have
clients staying around. Part of our process of moving to maxscanrows and
maxresults is refactoring everyone's p4 clients. I've found that negative
mappings act in surprising ways, causing you to break those limits earlier than
one would expect.
Once we get done with that, we'll rebalance. Last time we rebalanced, our DB
have dropped from 26gb to 22gb, so it wasn't a huge savings.
Another thing I've done is write a perl script which processes a checkpoint and
looks at pv's for db.have and counts the number per client, so that I can smack
people that have more files than they could ever hope to use. I can pretty
much take that number and divide by 250,000 and get the number of branches they
have mapped.
j
-----Original Message-----
From: Grills, Jeff
Sent: Friday, November 19, 2004 5:55 PM
To: 'jab'
Cc: Perforce Users Mailing List
Subject: RE: [p4] Large installations and performance
We have 266 clients for 117
j
-----Original Message-----
From: jab [mailto:jab@xxxxxxxxx]
Sent: Friday, November 19, 2004 5:38 PM
To: Grills, Jeff
Cc: Perforce Users Mailing List
Subject: Re: [p4] Large installations and performance
On Nov 19, 2004, at 2:20 PM, Grills, Jeff wrote:
> Anyone see anything suspicious? Anyone have comparable or larger
> systems that perform well? If so, what sort of setup are you running?
The size of db.have is troubling.
Is it possible that you're creating temporary client workspaces as an
artifact of a build process, and not reusing them nor deleting them?
Ultimately, that can keep entries in the db.have - which is getting
larger, I'd bet. (There might be ways to use labels or path+changenum
strategies, to guarantee reproducible releases. Labels will move the
data issue to another table, but it'll be out of the way of normal
'client workspace' traffic.)
Also, it might be unrealistic to have every branch copied into every
client workspace. It's worth considering what the developers do, and
how small modifications to their development process might use this
tool more efficiently. (Do they have to map in every branch and sync
every file? Each file retrieved is a row in the db.have table.)
Check with the folks in Tech Support. They know their stuffings, which
is particularly important around this time of November... ;-)
-Jeff Bowles, Perforce Consulting Partner
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
|
