Flush attribute to memory first if attribute saver has a

read guard and we are using a spinning disk.  This reduces
the time the read guard is held (and corresponding extra
long term memory usage due to large hold lists) at the cost
of a temporary memory usage spike while flushing attribute.

1 files changed, 3 insertions, 1 deletions

diff --git a/searchcore/src/apps/tests/persistenceconformance_test.cpp b/searchcore/src/apps/tests/persistenceconformance_test.cpp
index c9ce9b88477..a988ed99ace 100644
--- a/searchcore/src/apps/tests/persistenceconformance_test.cpp
+++ b/searchcore/src/apps/tests/persistenceconformance_test.cpp
@@ -19,6 +19,7 @@ LOG_SETUP("persistenceconformance_test");
 #include <vespa/searchlib/transactionlog/translogserver.h>
 #include <tests/proton/common/dummydbowner.h>
 #include <vespa/vespalib/io/fileutil.h>
+#include <vespa/vespalib/util/mock_hw_info.h>
 
 using namespace config;
 using namespace proton;
@@ -188,7 +189,8 @@ public:
                                _config_stores.getConfigStore(
                                        docType.toString()),
                                std::make_shared<vespalib::ThreadStackExecutor>
-                               (16, 128 * 1024)));
+                               (16, 128 * 1024),
+                               std::make_shared<vespalib::MockHwInfo>()));
     }
 };