diff options
| author | Tor Brede Vekterli <vekterli@yahoo-inc.com> | 2017-12-04 11:31:29 +0000 |
|---|---|---|
| committer | Tor Brede Vekterli <vekterli@yahoo-inc.com> | 2017-12-04 13:06:46 +0000 |
| commit | 952a877611d657cfa0166b14699c8731b18f7587 (patch) | |
| tree | c1b4330b9dc512c3ffbf845e626857ddcd801982 /storage/src/tests/storageserver/communicationmanagertest.cpp | |
| parent | d164fbb93e277ef23ab610320a7cf8556e3c036e (diff) | |
Remove memory manager component from content layer
We already have resource utilization tracking in both MessageBus
and the search core. The memory manager has never been auto-scaled
based on the hardware present and adds a _lot_ of complexity without
having any known instances where it has actually saved the day.
Removing it also removes a mutex on the message hot path.
If we need such functionality in the future, should design a lock-free
solution.
Cleanup
Diffstat (limited to 'storage/src/tests/storageserver/communicationmanagertest.cpp')
| -rw-r--r-- | storage/src/tests/storageserver/communicationmanagertest.cpp | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/storage/src/tests/storageserver/communicationmanagertest.cpp b/storage/src/tests/storageserver/communicationmanagertest.cpp index 5111368dd1c..cd5dd2a01a4 100644 --- a/storage/src/tests/storageserver/communicationmanagertest.cpp +++ b/storage/src/tests/storageserver/communicationmanagertest.cpp @@ -6,7 +6,6 @@ #include <vespa/messagebus/rpcmessagebus.h> #include <vespa/storageapi/message/persistence.h> #include <vespa/storage/frameworkimpl/component/storagecomponentregisterimpl.h> -#include <vespa/storageframework/defaultimplementation/memory/nomemorymanager.h> #include <tests/common/teststorageapp.h> #include <tests/common/dummystoragelink.h> #include <tests/common/testhelper.h> |