[p4] Automated testing of a new installation

[Michael McTernan]

Hi Noah,

I was hoping for some test script(s) that would run against a new
installation of a server, check in some files, perform many operations on
the files (in parallel would be great), and then report the time taken to
complete.  

The objective is mainly to ensure that the system is stable under load. 

Generally we don't see performance issues with Perforce, so timing a set run
of commands against our old and new server would probably be enough to give
us confidence that the new installation is no worse than the old.

If someone else has already developed such scripts, it would give us a great
leg up and save us redeveloping something to meet these requirements.

How do other people test new server installations?

Regards,

Mike

> -----Original Message-----
> From: Noah Salzman [mailto:noah at ncircle.com]
> Sent: 06 June 2006 23:40
> To: Michael McTernan
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Automated testing of a new installation
> 
> 
> On Jun 6, 2006, at 10:12 AM, Michael McTernan wrote:
> 
> >
> >> Are you looking for things that (specifically thrash p4d)
> >
> > Yes - specifically thrashing p4d.  Ideally collecting some
> > performance data
> > for comparison against the old system, although that maybe a lot to
> > ask.
> 
> 
> Well, hopefully others on this list will have some good ideas... the
> first ones that pop into my head are perhaps too simplistic:
> 
> 1) p4 verify -q //...
> 
> 2) p4 sync //... > /dev/null
> 
> 3) p4 print //... > /dev/null
> 
> 4) p4 integ repeatedly?
> 
> 
>     --Noah--
> 
>