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 /storageframework/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 'storageframework/CMakeLists.txt')
| -rw-r--r-- | storageframework/CMakeLists.txt | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/storageframework/CMakeLists.txt b/storageframework/CMakeLists.txt index 5a4b2e02372..a3414a8b05c 100644 --- a/storageframework/CMakeLists.txt +++ b/storageframework/CMakeLists.txt @@ -11,12 +11,10 @@ vespa_define_module( src/vespa/storageframework/defaultimplementation src/vespa/storageframework/defaultimplementation/clock src/vespa/storageframework/defaultimplementation/component - src/vespa/storageframework/defaultimplementation/memory src/vespa/storageframework/defaultimplementation/thread src/vespa/storageframework/generic src/vespa/storageframework/generic/clock src/vespa/storageframework/generic/component - src/vespa/storageframework/generic/memory src/vespa/storageframework/generic/metric src/vespa/storageframework/generic/status src/vespa/storageframework/generic/thread @@ -28,7 +26,6 @@ vespa_define_module( TESTS src/tests src/tests/clock - src/tests/memory src/tests/status src/tests/thread ) |