Reputation: 203
I am doing load test on an application that uses Vespa as a database. I have some sample records for which I am doing the test. Now when I run the load test for the first time, Vespa caches the query result which affects our next test scenario results.
Is there a way so that we can disable caching of results for the query for testing purposes and then enable it again.
I am hoping to get the same response time from Vespa after running the same query for the second time.
Even though I have implemented the below code in the services.xml file of our Vespa application. The response time drastically changed for the second time query.
<content id="content" version="1.0">
<engine>
<proton>
<tuning>
<searchnode>
<summary>
<store>
<cache>
<maxsize>0</maxsize>
<compression>
<type>none</type>
</compression>
</cache>
</store>
</summary>
</searchnode>
</tuning>
</proton>
</engine>
...
</content>
Upvotes: 5
Views: 148
Reputation: 366
Vespa does not cache the query result, and with the summary cache disabled there is no caching at all.
Vespa (like many other databases) takes a while to "warm up" - due to effects like JIT compilation of Java code, OS disk caches, CPU instruction/data caches and so on. You should begin by doing enough queries first that the query latency reaches a steady state.
Upvotes: 2