diff options
| author | Geir Storli <geirst@verizonmedia.com> | 2020-10-26 09:57:17 +0000 |
|---|---|---|
| committer | Geir Storli <geirst@verizonmedia.com> | 2020-10-26 09:57:17 +0000 |
| commit | f41815b4118b3e98dce00a5a94be94334fe6e29c (patch) | |
| tree | 821038e740a38a7917f65cd50d5b8ebf7f948e22 /configdefinitions | |
| parent | ae99f6bd8f0c28ae24fd814c9ee164de86b649b8 (diff) | |
Add support for async message handling when scheduling storage messages in FileStorManager.
When turned on, the calling thread (e.g. FNET network thread when using Storage API RPC)
gets the next async message to handle (if any) as part of scheduling a storage message.
This async message is then handled by the calling thread immediately,
instead of going via a persistence thread.
Diffstat (limited to 'configdefinitions')
| -rw-r--r-- | configdefinitions/src/vespa/stor-filestor.def | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/configdefinitions/src/vespa/stor-filestor.def b/configdefinitions/src/vespa/stor-filestor.def index bf1b4294b5b..1cec77832a7 100644 --- a/configdefinitions/src/vespa/stor-filestor.def +++ b/configdefinitions/src/vespa/stor-filestor.def @@ -63,3 +63,11 @@ enable_merge_local_node_choose_docs_optimalization bool default=true restart ## if splitting is expensive, but listing document identifiers is fairly cheap. ## This is true for memfile persistence layer, but not for vespa search. enable_multibit_split_optimalization bool default=true restart + +## Whether or not to use async message handling when scheduling storage messages from FileStorManager. +## +## When turned on, the calling thread (e.g. FNET network thread when using Storage API RPC) +## gets the next async message to handle (if any) as part of scheduling a storage message. +## This async message is then handled by the calling thread immediately, +## instead of going via a persistence thread. +use_async_message_handling_on_schedule bool default=false restart |