diff options
| author | Simon MacMullen <simon@rabbitmq.com> | 2010-12-02 12:39:32 +0000 |
|---|---|---|
| committer | Simon MacMullen <simon@rabbitmq.com> | 2010-12-02 12:39:32 +0000 |
| commit | 7d68ac0e63c3be4571591ef8dfdf6a15da15801d (patch) | |
| tree | f42d7d036fd4e2480a32049696a6c2fb62a9e776 | |
| parent | ed6477ab5915428188c2b0fbd5b334c1cddce5de (diff) | |
| download | rabbitmq-server-bug23532.tar.gz | |
Tone down the claims in the optimisation comment.bug23532
| -rw-r--r-- | src/rabbit_writer.erl | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/rabbit_writer.erl b/src/rabbit_writer.erl index 9c32c272..12b34bcd 100644 --- a/src/rabbit_writer.erl +++ b/src/rabbit_writer.erl @@ -188,8 +188,8 @@ assemble_frames(Channel, MethodRecord, Content, FrameMax, Protocol) -> %% We optimise delivery of small messages. Content-bearing methods %% require at least three frames. Small messages always fit into %% that. We hand their frames to the Erlang network functions in one -%% go, which leads to more efficient processing in the runtime and a -%% greater chance of coalescing into fewer TCP packets. +%% go, which may lead to somewhat more efficient processing in the +%% runtime and a greater chance of coalescing into fewer TCP packets. %% %% By contrast, for larger messages, split across many frames, we want %% to allow interleaving of frames on different channels. Hence we |