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/CMakeLists.txt | |
| 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/CMakeLists.txt')
| -rw-r--r-- | storage/CMakeLists.txt | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/storage/CMakeLists.txt b/storage/CMakeLists.txt index 24d5a2d27f2..5c24d4adb3b 100644 --- a/storage/CMakeLists.txt +++ b/storage/CMakeLists.txt @@ -35,7 +35,6 @@ vespa_define_module( src/vespa/storage/distributor/operations/external src/vespa/storage/distributor/operations/idealstate src/vespa/storage/frameworkimpl/component - src/vespa/storage/frameworkimpl/memory src/vespa/storage/frameworkimpl/status src/vespa/storage/frameworkimpl/thread src/vespa/storage/persistence @@ -60,7 +59,6 @@ vespa_define_module( src/tests/common src/tests/common/hostreporter src/tests/distributor - src/tests/frameworkimpl/memory src/tests/frameworkimpl/status src/tests/persistence src/tests/persistence/common |