[p4] Improve robustness on poor networks?
Shiv Sikand
shiv at icmanage.com
Wed Aug 2 17:49:47 PDT 2006
Rusty,
Actually, this is not entirely true. With a little bit of magic you can
use this localized server to populate a P4P, making your network
transfers from the main server very efficient and reliable over poor
networks. Again, Unix/GNU-Linux required.
Cheers,
Shiv
Russell C. Jackson wrote:
> And it is a read only cache of the main server. It doesn't offer the
> same functionality that P4Proxy does in that you can't use it as cache
> to production server.
>
> Thanks,
> Rusty
>
> --------------------------------------------------
> RCJackson Consulting
> Perforce Consulting Partner and Certified Trainer
> --------------------------------------------------
> Russell C. Jackson
> 211 River Oaks Lane
> Russellville, AR 72802
> --------------------------------------------------
> rusty at rcjacksonconsulting.com
> http://www.rcjacksonconsulting.com
> tel: 479-696-9710
> fax: 479-967-0963
> mobile: 479-747-3845
> --------------------------------------------------
>
>
>
>
> Shiv Sikand wrote:
>> Chris,
>>
>> IC Manage sells a product called icmrep. icmrep can replicate both db
>> and depot files in near real time from your main office p4d to give
>> you a localized p4d for sync and other read operations. The
>> replication is highly tolerant of poor links (latency, bandwidth,
>> dropped packets etc) and is transactionally consistent with your
>> master p4d. This solution can therefore eliminate your problem since
>> your users will be running against a local p4d.
>>
>> The only requirement which can be a potential show stopper is that the
>> replicator is only supported on Unix/GNU-Linux.
>>
>> Thanks,
>> Shiv
>>
>>
>>
>>> Message: 5
>>> Date: Tue, 1 Aug 2006 17:07:29 -0700
>>> From: "Chris Weiss" <chris.weiss at gmail.com>
>>> Subject: [p4] Improve robustness on poor networks?
>>> To: "Perforce Users" <perforce-user at perforce.com>
>>> Message-ID:
>>> <b91cc5d50608011707u74f07b22v1b4c5f1d40aae7e8 at mail.gmail.com>
>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>
>>> Our network's a bit spotty - if our pipe to the outside world gets
>>> saturated, we start losing packets. This spells trouble for our remote
>>> office as they'll be in the middle of a big sync and P4 will throw a
>>> WSAE_TIMEOUT.
>>>
>>> Does anyone have any tips (outside of QoS) on ways to avoid P4
>>> dropping connections so easily? We've already got a proxy server in
>>> the remote office, but it still disconnects far too often due to
>>> packet loss.
>>>
>>>
>>
>> _______________________________________________
>> perforce-user mailing list - perforce-user at perforce.com
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>
>>
>>
>>
>
More information about the perforce-user
mailing list