bennett at jmisoftware.com
Wed Oct 18 09:42:58 PDT 2000
What do you mean by "access". Different commands usually have different
performance issues. We had a problem on one of our machines where sync was
slow as hell, but the rest of the behavior tended to be normal speed. That
turned out to be weird registry settings affecting overall network transfer
speeds. (We fixed it using a utility called SpeedTec by Montana Software --
On other machines, syncs were fast, but expanding the directory tree was
slow. That turned out to be the issue others have mentioned - using the
machine name instead of the IP address -- every time it did a command it had
to re-resolve the machine name, and that itself was slow.
> From: Arno Ruzicka <arno.ruzicka at marconi.com>
> Date: Wed, 18 Oct 2000 12:08:15 -0400
> To: "Doug Ditillo" <dougditillo at wamsystems.com>, "John Griffin"
> <JohnG at sedonanetworks.com>, <perforce-user at perforce.com>
> Subject: Re: [p4] p4Win
> Thanks for sharing your experience, which I thought, would solve our
> problem with remote depot. Unfortunately, after changing the server name to
> IP address, the problem still persists.
> We have one depot on server here in Ottawa (Canada) and the other depot on
> server in Dublin (Ireland, which we here in Ottawa have setup as a remote).
> To access the Dublin remote depot in P4WIN takes more than an hour.
> After reading your suggestion I was hoping, that changing the address in
> Perforce Depot Specification for the remote Dublin depot from server name
> to its IP address would improve the time, but it did not happen.
> Does anybody have any explanation for this or a hint of how to improve
> this? Is there any other parameter to be set up? What is happening that it
> take such a long time?
> Thanks for any suggestions,
> At 04:18 PM 10/17/00 -0400, Doug Ditillo wrote:
>> Recently we discovered that our P4win performance was suffering because we
>> were using the computer name instead of the IP address in the client's
>> P4Port setting. When we changed it, the performance improved immensely.
>> There is a note in the Perforce documentation on this issue.
>> ----- Original Message -----
>> From: "John Griffin" <JohnG at sedonanetworks.com>
>> To: <perforce-user at perforce.com>
>> Sent: Tuesday, October 17, 2000 3:48 PM
>> Subject: [p4] p4Win
>>> in the environment that we are running here, p4 commands work just fine
>>> p4Win is extremely slow. Should I think of this as natural behavior or is
>>> there something going on here?
>>> perforce-user mailing list - perforce-user at perforce.com
>> perforce-user mailing list - perforce-user at perforce.com
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user