[p4] Deleted branches affecting the Perforce performance
Russell C. Jackson
rusty at rcjacksonconsulting.com
Fri May 26 19:26:18 PDT 2006
That doesn't solve the performance problem he is referring to here.
Perforce still has that information in its db files, and still has to
scan it in certain situations.
Perforce needs an archive command. I have been asking for one for
several years now.
Thanks,
Rusty
Stephen Vance wrote:
> Rather than delete obsolete branches, exclude them from permissions in
> the protection table. Just be sure to leave your "super" lines below the
> exclusions.
>
> Steve
>
> BAY wrote:
>
>> All,
>>
>> I discussed this subject with P4 helpdesk many times and I wonder if anyone of you can enlight me.
>>
>> We all create branches and they will get deleted one day. Since P4 is source control system, the deleted files are still exist in the P4 server.
>>
>> Issue: Althought we can configure the P4 client not to display the deleted files or directories. However, P4 will still scan and as a result, and this will affect the performance.
>>
>> Question: Any of you experience this and come up with a solution? I asked them for an feature enhancement for "archiving tool or function". I am running 2004.2 and i believe that is also a problem for newer version. Comments?
>>
>> Thanks.
>>
>> Baz
>>
>>
>> _______________________________________________
>> perforce-user mailing list - perforce-user at perforce.com
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>
>>
>>
> _______________________________________________
> 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