Proposal: new fsfs.conf properties

1. compression-exempt-suffixes = mp3,mp4,jpeg 2. deltification-exempt-suffixes = mp3,mp4,jpeg Regardless of the setting of 'compression-level', #1 above two mean certain things can skip the compression attempt. It must give up at a certain point right? Same for deltification re #2 I'm

Re: Expected speed of commit over HTTP?

Great insights, Stefan. So 'cp' with that sync, timed as you outline is averaging 3x slower than the cp as I had it before. Thus, that same cp with sync tacked on, is 3x faster that the curl PUT over HTTP. That's within the place where any speedup spent on the handoff of between apache modules

Re: Expected speed of commit over HTTP?

On 07.07.2017 01:10, Paul Hammant wrote: With autorevision set to 'on' and curl: Reverence speed for boot drive to USB3 spinning platter 4TB thing: paul@paul-HiBox:~$ time cp /home/paul/clientDir/seven /media/paul/sg4t/sevenb real0m1.539s That isn't exactly accurate - you write

Re: [PATCH] Tweak the SHA-1 FAQ entry

Bert Huijben writes: > Except for s/ it / is / on this line, +1... Looks very good! Jacek Materna writes: > Fair enough! > > Rest looks great. I fixed the typo and committed the patch in https://svn.apache.org/r1801202 Regards, Evgeny Kotkov

Re: svn commit: r1801108 - in /subversion/trunk/subversion/bindings/javahl/native: Array.cpp CreateJ.cpp Iterator.cpp OperationContext.cpp RemoteSession.cpp RevisionRangeList.cpp

On 06.07.2017 23:11, Philip Martin wrote: Philip Martin writes: I've upgraded my JDK and it produced all these warnings. Excellent to see these warnings being addressed! There is a second class of warnings of the form: WARNING: JNI local refs: 57, exceeds

Re: [PATCH] Tweak the SHA-1 FAQ entry

Fair enough! Rest looks great. -- Jacek Materna Assembla CTO +1 210 410 7661 +48 578 296 708 Sent from my Mobile Device > On Jul 7, 2017, at 5:47 PM, Evgeny Kotkov wrote: > > Jacek Materna writes: > >> Shouldn't vulnerability / shattered

Re: [PATCH] Tweak the SHA-1 FAQ entry

Jacek Materna writes: > Shouldn't vulnerability / shattered remain a keyword? I believe it was > a comment in the patch I submitted - just wondering about google-ness > of it... shattered has a lot of google juice. I was thinking about turning this FAQ entry into a more or

Re: [PATCH] Tweak the SHA-1 FAQ entry

Shouldn't vulnerability / shattered remain a keyword? I believe it was a comment in the patch I submitted - just wondering about google-ness of it... shattered has a lot of google juice. collision vs. 'shattered / vulnerability' Otherwise more complete verbiage is always good. On Fri, Jul 7,

RE: [PATCH] Tweak the SHA-1 FAQ entry

> -Original Message- > From: Evgeny Kotkov [mailto:evgeny.kot...@visualsvn.com] > Sent: vrijdag 7 juli 2017 16:46 > To: Subversion Development > Subject: [PATCH] Tweak the SHA-1 FAQ entry > > Hi all, > > I made an attempt to tweak the SHA-1 FAQ entry (which

Re: svn commit: r1801108 - in /subversion/trunk/subversion/bindings/javahl/native: Array.cpp CreateJ.cpp Iterator.cpp OperationContext.cpp RemoteSession.cpp RevisionRangeList.cpp

Branko Čibej writes: > On 06.07.2017 23:11, Philip Martin wrote: >>// Create a local frame for our references >> - env->PushLocalFrame(LOCAL_FRAME_SIZE); >> + env->PushLocalFrame(LOCAL_FRAME_SIZE + 100); > > Mmph ... it kinda hurts to see how limited the JNI API is in

[ANNOUNCE] Apache Subversion 1.8.18 released

I'm happy to announce the release of Apache Subversion 1.8.18. Please choose the mirror closest to you by visiting: http://subversion.apache.org/download.cgi#supported-releases This release fixes a bug where a repository would fail to reject two files having identical SHA-1 checksums [1].

Re: Expected speed of commit over HTTP?

On 07.07.2017 12:10, Paul Hammant wrote: > ~/.subversion/servers contains a line that's tunable, right: > > # http-compression = no > > And per comment, tack on: > > --config-option=servers:global:http-compression=no . > > I'll report back the results. > > > How is Apache and its modules

Re: svn commit: r1801108 - in /subversion/trunk/subversion/bindings/javahl/native: Array.cpp CreateJ.cpp Iterator.cpp OperationContext.cpp RemoteSession.cpp RevisionRangeList.cpp

On 06.07.2017 23:11, Philip Martin wrote: > Philip Martin writes: > >> I've upgraded my JDK and it produced all these warnings. Adding the exception checks is correct. Rewriting everything to use the jniwrapper abstraction would be even better, but that's a huge-ish

Re: svn commit: r1801108 - in /subversion/trunk/subversion/bindings/javahl/native: Array.cpp CreateJ.cpp Iterator.cpp OperationContext.cpp RemoteSession.cpp RevisionRangeList.cpp

"Bert Huijben" writes: > Should we backport these to 1.9.x? I don't know, possibly. See my other mail to dev for the questions I have about these checks. -- Philip

RE: svn commit: r1801108 - in /subversion/trunk/subversion/bindings/javahl/native: Array.cpp CreateJ.cpp Iterator.cpp OperationContext.cpp RemoteSession.cpp RevisionRangeList.cpp

> -Original Message- > From: phi...@apache.org [mailto:phi...@apache.org] > Sent: donderdag 6 juli 2017 22:56 > To: comm...@subversion.apache.org > Subject: svn commit: r1801108 - in > /subversion/trunk/subversion/bindings/javahl/native: Array.cpp CreateJ.cpp > Iterator.cpp

Re: Expected speed of commit over HTTP?

On Fri, Jul 7, 2017 at 8:54 AM, Jacek Materna wrote: > Paul, > > Got back from Ops. We don't have anything "special" setup other than what > already been mentioned. Overall the defining metrics for commit performance > are: ssh vs https, rtt on the network path and

Re: Expected speed of commit over HTTP?

Paul, Got back from Ops. We don't have anything "special" setup other than what already been mentioned. Overall the defining metrics for commit performance are: ssh vs https, rtt on the network path and "randomness" of the blobs going up. No magic params on our end. We have it tuned the max