Hi Aerospike Community,
I am testing out Aerospike C client for Windows. The old client is the libevent client mentioned in Aerospike page:
The new client being integrated is the asynchronous C libevent:
Test is performed on a server that makes 1400 asynchronous get requests to Aerospike cluster of 5 nodes.
The old client is consistently timing out at less than 1% of total request.
The new client is consistently timing out at around 5% of total request.
What is the reason of this high time out rate? Does the way I use the clients produce different requests to the server?
Snippet of old client usage:
uint32_t requestTimeoutMs = 10; int ret = ev2citrusleaf_get(cluster, nameSpace, setName, &key, binNames, 1, requestTimeoutMs, GetCallBack, (void*)udata, eventLoop);
Snippet of new client usage:
as_event_create_loops(1);//called during client construciton uint32_t requestTimeoutMs = 10; as_policy_read readPolicy; as_policy_read_init(&readPolicy); readPolicy.base.total_timeout = requestTimeoutMs; int ret = aerospike_key_select_async(cluster, &err, &readPolicy, &key, binNames, GetCallBack, (void *)udata, nullptr, nullptr);