14 messages in com.perforce.perforce-userp4Win with a UNIX server| From | Sent On | Attachments |
|---|---|---|
| Anth...@pilotsw.com | 25 Aug 1998 12:09 | |
| Joha...@xpress.se | 25 Aug 1998 12:34 | |
| Babu...@Mitel.COMBabu_Somisetty | 25 Aug 1998 12:59 | |
| Anth...@pilotsw.com | 25 Aug 1998 13:41 | |
| WesP...@softweyr.com | 25 Aug 1998 21:03 | |
| WesP...@softweyr.com | 25 Aug 1998 22:15 | |
| Nick...@pobox.com | 26 Aug 1998 04:52 | |
| Anth...@pilotsw.com | 26 Aug 1998 06:21 | |
| Fred...@mydata.se | 26 Aug 1998 06:34 | |
| Raym...@orion.no | 26 Aug 1998 06:55 | |
| RobC...@within.com | 26 Aug 1998 07:25 | |
| Rich...@geodesic.com | 26 Aug 1998 08:08 | |
| Nick...@pobox.com | 26 Aug 1998 08:21 | |
| Anth...@pilotsw.com | 27 Aug 1998 05:37 |
| Subject: | p4Win with a UNIX server |
|---|---|
| From: | Rich...@geodesic.com (Rich...@geodesic.com) |
| Date: | 08/26/1998 08:08:36 AM |
| List: | com.perforce.perforce-user |
At 1998-08-26 10:25 -0400, Rob Chandhok wrote:
At 12:52 PM +0100 8/26/98, Nick Barnes wrote:
With a fair-sized depot (p4 files //... | wc says 116296 files), served from FreeBSD, across a slowish transatlantic connection (IP latency 300-1000ms, bandwidth 10-30KB/sec), p4win can take 30-45 _minutes_ to start up. On a machine on the same ethernet as the server it is much faster but still several minutes. We have reported this to Perforce. We haven't tried with an NT server (why would anyone want to serve anything from NT? :->)
Not to be snippy, but are you surprised that p4win performs the way it does with a connection of this slow speed? I'm not.
Surprised? Yes. Perforce bills itself as "The Fast Software Configuration Management System" but is failing in this respect. There's no need for it to do all this work when it first starts the client, and it shouldn't. It should only do what's necessary to get the user started.
It still takes about 5-10 minutes to start on a local 100Mb/s ethernet, so it's not just the network connection that's at fault.
That's why over slow lines I recommend just using the command line tools. That's about as efficient as you can get. That isn't to say p4win couldn't be improved (like waiting to fetch information until you ask for that view), but at least you have the command line stuff -- quite a reasonable tool to use over slow links.
Agreed, this is a workaround, but my users demand GRAPHICS, and you the P4Win client makes browsing the repository possible for non-technical people.