On 04/07/2011 07:29 AM, Stefan Sperling wrote: > Neels has set up his performance benchmarks to run on the svn VM > we have at apache.org.
[...] > Below are the results of the latest run. > They're probably a bit hard to decipher as is. The plan is to make the > scripts produce more easily digestable results and then send results > to dev@ on a weekly basis. Actually, I find them fairly straightforward to interpret. I particularly like the comparison approach, providing multiplier values to demonstrate slowerthan/fasterthan and the associated degree of either! What's missing, I suppose, is an explanation of what each operation is truly doing. By the varying N values, I'm guessing that there are some number of high-level scenarios in play, but each step of the scenario is measured. That is, if the scenario is "merge a branch into the trunk", you will have measured each add of each file and dir, each commit to built up some history, the copy to make the branch, and the merge itself, plus maybe some status/proplist to verify state. Is that (roughly) what's going on? In that case, explaining each "add" (for example) would be unwieldy. But maybe explaining the high-level scenarios would be useless? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
