add links to tickets.
[Imported from Trac: page Performance, version 39]
parent
ee4c99f01d
commit
3770e9a000
|
@ -1,6 +1,8 @@
|
||||||
(See also copious notes and data about performance of older versions of Tahoe-LAFS, archived at Performance/Old.)
|
(See also copious notes and data about performance of older versions of Tahoe-LAFS, archived at Performance/Old.)
|
||||||
|
|
||||||
In September 2011 Brian Warner did thorough benchmarks on a four-machine grid of dedicated physical hardware which wasn't doing any other tasks except for running the benchmarks: [see here](Performance)/Sep2011
|
In September 2011 Brian Warner did thorough benchmarks on a four-machine grid of dedicated physical hardware which wasn't doing any other tasks except for running the benchmarks: [see here](Performance)/Sep2011.
|
||||||
|
|
||||||
|
Here are two tickets about building automation to measure and display performance measurements: #1406, #1530
|
||||||
|
|
||||||
In late 2010 Kyle Markley did some benchmarking of what were then the release candidates for Tahoe-LAFS v1.8.0. This helped us catch two major performance regressions in Brian's New Downloader and helped make Tahoe-LAFS v1.8.0 into an excellent new release (see epic ticket #1170 for mind-numbing details). Kyle also contributed code for his benchmarking scripts (in Perl), but nobody to my knowledge has yet tried to re-use that script.
|
In late 2010 Kyle Markley did some benchmarking of what were then the release candidates for Tahoe-LAFS v1.8.0. This helped us catch two major performance regressions in Brian's New Downloader and helped make Tahoe-LAFS v1.8.0 into an excellent new release (see epic ticket #1170 for mind-numbing details). Kyle also contributed code for his benchmarking scripts (in Perl), but nobody to my knowledge has yet tried to re-use that script.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue