diff options
| author | bors <bors@rust-lang.org> | 2013-11-11 19:31:14 -0800 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-11-11 19:31:14 -0800 |
| commit | 8b4683d79d4b74f53808470cd2f98b23a0af9b93 (patch) | |
| tree | a3383998a3d2db2ca06390936165af98d156dde0 /src/etc/combine-tests.py | |
| parent | 86787f8befe0f8971f27bd15be1e16ec7aa99e7e (diff) | |
| parent | cdf7d63bfce33d2390e3a0a27e01a07f262834e7 (diff) | |
| download | rust-8b4683d79d4b74f53808470cd2f98b23a0af9b93.tar.gz rust-8b4683d79d4b74f53808470cd2f98b23a0af9b93.zip | |
auto merge of #10424 : alexcrichton/rust/optimize-buffered, r=brson
I was benchmarking rust-http recently, and I saw that 50% of its time was spent creating buffered readers/writers. Albeit rust-http wasn't using std::rt::io::buffered, but the same idea applies here. It's much cheaper to malloc a large region and not initialize it than to set it all to 0. Buffered readers/writers never use uninitialized data, and their internal buffers are encapsulated, so any usage of uninitialized slots are an implementation bug in the readers/writers.
Diffstat (limited to 'src/etc/combine-tests.py')
0 files changed, 0 insertions, 0 deletions
