14 messages in com.perforce.perforce-userp4Win with a UNIX server
FromSent OnAttachments
Anth...@pilotsw.com25 Aug 1998 12:09 
Joha...@xpress.se25 Aug 1998 12:34 
Babu...@Mitel.COMBabu_Somisetty25 Aug 1998 12:59 
Anth...@pilotsw.com25 Aug 1998 13:41 
WesP...@softweyr.com25 Aug 1998 21:03 
WesP...@softweyr.com25 Aug 1998 22:15 
Nick...@pobox.com26 Aug 1998 04:52 
Anth...@pilotsw.com26 Aug 1998 06:21 
Fred...@mydata.se26 Aug 1998 06:34 
Raym...@orion.no26 Aug 1998 06:55 
RobC...@within.com26 Aug 1998 07:25 
Rich...@geodesic.com26 Aug 1998 08:08 
Nick...@pobox.com26 Aug 1998 08:21 
Anth...@pilotsw.com27 Aug 1998 05:37 
Subject:p4Win with a UNIX server
From:Anth...@pilotsw.com (Anth@pilotsw.com)
Date:08/25/1998 01:41:29 PM
List:com.perforce.perforce-user

Ping executes in about the same time against both machines.

"p4 info" also returns just as fast from either and it seems like the command line - p4 foo - works quite speedily too against UNIX. When a developer from the UK did a sync against both machines he got average speeds of 0.76 seconds per file on NT and 0.79 on the UNIX box. Definitely no 14 second waits for a command to complete or anything. As a wild guess it seems like p4win spends quite a while sorting through the metadata - after a submit I get a lengthy wait cursor. And at p4Win start up after displaying the various icons that represent the depot it also spends a long time with an unusable cursor.

Its a sun machine running solaris with a nfs mounted 'toaster' on a dedicated optical fiber connection. I don't know the specifics, although I could get them if it really seems like this might make a big difference. The NT (4.0 sp3) box has a 120mhz pentium with a scsii hard disk. Roughly 500 source and binary files in each depot.

In both cases I do set p4port=xxx.xxx.xxx.xxx:1666, not hostname:1666. -- Tony K.

Babu_Somisetty at Mitel.COM on 08/25/98 03:59:29 PM

To: jgroth at xpress.se cc: Anthony Kolarik, perforce-user at perforce.com Subject: Re: p4Win with a UNIX server

From: Babu Somisetty at MITEL on 08/25/98 12:59 PM PDT Anthony ... Could you explain a bit more about your setup. Where are your server and client files?

Johan ... I thought NFS comes into picture only when you try to access UNIX disks on NT or vice versa. Doesn't p4 communicate with p4d using tcp/ip? Why would NFS be an issue here?

---- Babu

jgroth at xpress.se on 08/25/98 12:34:33 PM

To: Anthony_Kolarik at pilotsw.com cc: perforce-user at perforce.com (bcc: Babu Somisetty/USA/Mitel) Subject: Re: p4Win with a UNIX server

Anthony Kolarik wrote:

Starting p4win against an NT based p4d takes around 1 second on my NT workstation machine. Starting it against a solaris machine takes about 14 seconds. I have the same depot under both servers for testing purposes. (By which I mean I ported it to UNIX from NT.) I also get a long wait when I start the VC++ IDE - which incorporates p4 through a version control interface of some sort. This wait seems even longer than 14 seconds and adds to the already lengthy delay while the IDE itself gets a grip.

Any idea what might cause such a difference in response and/or what I could do to speed it up with the UNIX server? Thanks, -- Tony K.

My guess would be that you access the UNIX system with NFS. NT's implementation of NFS is incredible slow. SMB is a much better solution for accessing a UNIX file system from NT (SAMBA is one product that comes to mind, and is free). ///Johan

--- +-----------------------+---------------------------------------+ | Johan Groth | jgroth(at)xpress.se | | Kupolen Data | Johan.Groth(at)ein.ericsson.se | | Karlstad, Sweden | | +-----------------------+---------------------------------------+