[p4] How much traffic is too much?

[Jeff A. Bowles]

I would start by having all users set their GUI refresh time to
"really long intervals".
Those refreshes have a cost, in terms of queries and read-locks on
tables and so on,
that a large site will certainly notice.

Also, have GUI users close blue-triangle changelist info (in p4win) so that they
don't refresh info about other users/clients by default. ("Look, but close after
looking.")

A histogram (two, actually - one measuring number of each command run,
and one measuring number of client workspaces used) will tell you a lot.
A time-line that shows how many concurrent p4 commands at a given moment,
would be really useful.

I agree with Rusty Jackson - you have something that's too loaded for
comfort. Probably a script is running every second instead of every thirty
seconds, or  people are refreshing workspaces in a loop, or something like
that.

   -Jeff Bowles

ps. I'd set debugging to "track=1", to see everything. (Beware - it's
a file that can
grow. And grow. and...)


On 12/19/06, David Ferguson <daf at vmware.com> wrote:
> So ... In order to track down various performance metrics we came across an
> interesting stat...
> Our primary Perforce server is averaging 600 completed Perforce operations
> per second over a 2 day period. (by parsing the perforcelog set with
> server=3, track-3 and counting only the 'completed' operations).
>
> Is this below, at, or above average?  Or plain downright excessive (my
> personal guess).
>
> -daf
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>


-- 
---
Jeff Bowles - jab at piccoloeng.com