Hi @vsr1
Below is the query profile that i retrieved from the system:completed_requests. This result is newly executed query, since the last execution already removed from system:completed_requests.
[
{
“completed_requests”: {
“clientContextID”: “4f10fc3d-e5ec-4bb6-825d-cd4a53d8dad6”,
“elapsedTime”: “1h23m14.652918266s”,
“errorCount”: 0,
“mutations”: 1,
“node”: “localhost:8091”,
“phaseCounts”: {
“fetch”: 8741059,
“filter”: 16441842,
“indexScan”: 10590817
},
“phaseOperators”: {
“authorize”: 1,
“fetch”: 1,
“filter”: 8741047,
“indexScan”: 1,
“insert”: 1
},
“phaseTimes”: {
“authorize”: “11.801377ms”,
“fetch”: “1h12m11.635001049s”,
“filter”: “20m8.289706668s”,
“indexScan”: “1m23.645637015s”,
“insert”: “2.252214ms”,
“instantiate”: “69.911µs”,
“parse”: “6.522948ms”,
“plan”: “59.775311ms”,
“run”: “1h23m14.586347185s”
},
“remoteAddr”: “127.0.0.1:59471”,
“requestId”: “5abf9bd8-083f-4b85-a9ec-f79e25efac72”,
“requestTime”: “2021-01-15T08:32:15.662Z”,
“resultCount”: 1,
“resultSize”: 10,
“scanConsistency”: “unbounded”,
“serviceTime”: “1h23m14.65275854s”,
“state”: “completed”
}
}
]
also, below is the current setting of the query node:
{“auto-prepare”:false,“completed”:{“aborted”:null,“threshold”:1000},“completed-limit”:4000,“completed-threshold”:1000,“controls”:false,“cpuprofile”:“”,“debug”:false,“functions-limit”:16384,“keep-alive-length”:16384,“loglevel”:“INFO”,“max-index-api”:4,“max-parallelism”:1,“memprofile”:“”,“mutexprofile”:false,“n1ql-feat-ctrl”:12,“pipeline-batch”:16,“pipeline-cap”:512,“prepared-limit”:16384,“pretty”:false,“profile”:“off”,“request-size-cap”:67108864,“scan-cap”:512,“servicers”:56,“timeout”:0}
Does setting the max-parallelism before running the query might improve to the query performance? Or are there anything I can change to improve the query performance?
Regards,
Hartono