but, as brandon saw, we are doing multiple MD5 checksums. do we
really need all of them? is there a way to be more efficient here?
On Aug 29, 2006, at 5:48 AM, Daniel Berlin wrote:
> On 8/29/06, listman <listman@burble.net> wrote:
>>
>> so vdelta and md5 are the culprits?
>>
>> anything we can do in the short to improve this?
> Try the patch i sent, which disables vdelta.
>
> Also, you could disable checksum verification on every single read
> from the repository, and add it to svnadmin verify, if you wanted. I
> do this on gcc.gnu.org, trading immediate repo corruption detection
> for speed.
>
> (Why APR chose to reimplement MD5 instead of just taking advantage of
> OpenSSL, which is *installed* pretty much everywhere, and compilable
> everywhere else, and provides highly optimized versions, who knows)
>
> You will probably find vast resistance to disabling the repo read
> checksumming, but without doing that, you've pretty much lost the war
> for speed.
>
> This is true *even though* the client will detect the corruption
> anyway, because it is going to checksum it too and compare it to the
> repo checksum
>
> This is why you see multiple checksums happening.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 29 18:22:26 2006