Trying to understand if there are any fundamental difference between short queries and long queries. I am interested only in term of running Aerospike in-memory only.
- What is the difference between long queries and short queries? I understand that they are separated by the query-threshold option. But I want to know if there are any other difference. Are there any query optimization, IO optimization, bottleneck or throttling, any under the hood difference between long and short queries?
- Say if I have a record histogram of [40, 40, 10, 5, 1 … etc], does it mean I should change my query-threshold to 2 such that approximately 50% of my workloads are divided between long and short queries?
- Does high query-worker-threads affect query performance or just IO? and if so by how much? How should we determine how much query-worker-threads to allocate? Is it just bounded by how much memory we have?
- What is query-in-transactions-threads exactly. Does enabling it provides additional set of threads to help during queries? Or is it actually a replacement of existing query threads. Why should it be turned on? And what changes should we observe if we turn it on?
Appreciate for any insights. Cheers