[p4] Number of users to admins ratio
robert at vaccaperna.co.uk
Tue Mar 11 02:42:30 PDT 2008
Building on Nittin's point.
In general with Perforce, keeping the server running is very low overhead.
Then there is a certain amount of reactive ongoing admin work that will
always be there.
Then you get into proactive work such as automation which helps reduce the
reactive stuff. This also includes training, education and best practice
dissemination which make a big difference to the support load down the
I have seen some organisations under resource their configuration
management/Perforce team because it seems to work well enough as is. Yes the
server keeps going and users get a reasonable amount of support, but the
team doesn't have the time to do all they can, and the higher level view is
missing. This includes relationships with other parts of the organisation.
There are benefits of taking a real service oriented approach - providing a
configuration management service to the organisation, where Perforce happens
to be the tool in use. This is using the ideas from ITIL (ISO/IEC 20000),
which is a powerhouse here in the UK and Europe, but also in Canada and and
growing fast in the US.
<plug>Wearing my hat as Chair of the British Computer Society Specialist
Group for Change, Configuration and Release Management, can I recommend the
conference coming up on 8 & 9 July 2008, being running jointly with the
itSMF: www.bcs-cmsg.org.uk/conference/2008/index.shtml Programme to be
> We are 3 admin for approx 1500+ user's doing 20% support &
> 80% automation/bug-fix/future enhancement work.
> Please note more the automation lesser the support and
> higher the efficiency !
> "Jamison, Shawn" <sjamison at ciena.com> wrote:
> Quick question for the larger enterprise users of Perforce.
> What is your ratio of Perforce admins to users?
More information about the perforce-user