diff options
| author | Matthew Sackman <matthew@lshift.net> | 2009-07-02 17:35:48 +0100 |
|---|---|---|
| committer | Matthew Sackman <matthew@lshift.net> | 2009-07-02 17:35:48 +0100 |
| commit | a29a0b1e7e135e6b10f38900ff2426302fe8d1bd (patch) | |
| tree | 8674dcba4a82211c878799ecd26ed95e22e9b091 /docs | |
| parent | 9c1c368264f6845e36e710180291202290ac4b35 (diff) | |
| download | rabbitmq-server-git-a29a0b1e7e135e6b10f38900ff2426302fe8d1bd.tar.gz | |
well if we're going to not actually pull messages off disk when going to mixed mode, we may as well do it really lazily and not bother with any communication with the disk_queue. We just have a token in the queue which indicates how many messages we are expecting to get from the disk queue. This makes disk -> mixed almost instantaneous. This also means that performance is not initially brilliant. Maybe we need some way of the queue knowing that both it and the disk_queue are idle and deciding to prefetch. Even batching could work well. It's an endless trade off between getting operations to happen quickly and being able to get good performance. Dunno what the third thing is, probably not necessary, as you can't even have both of those, let alone pick 2 from 3!
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions
