Why a simple query is slow on nodejs?

[servermanager017]

Ahh ok thanks,

but how can I configure the idle timeout ? I see all timeouts but not idle

Client Settings | Couchbase Docs

[mreiche]

The behavior I described was for the Java SDK. The nodejs could be different.

For nodejs - it looks like you figured this out from your post in another thread …

Java Couchbase Client Config for higher throughput

I had the same problem. The first query takes 100-200ms. So all other does not take so long except when you have in one second no more request. Then again if you execute the query it takes 100-200ms but all other request are fast. It is because you have a idle_http_connection_timeout is default to 1000 (1 second). When you recieve every second requests your queries are fast. You can set the idle_http_connection_timeout to 5000 (5 seconds) then when you make a first query it takes 100-200ms but …

[00christian00]

If you care about performance use key value operations, n1ql is still slow and will probably be slow forever.
The only performant method of querying is to use views but it seem they are planning to deprecate them.

[mreiche]

Query will not be as fast as kv, because of the processing the statement and also because the result may need to be fetched from other nodes. But there are many things a query can do that kv cannot.

[vsr1]

@mreiche

SELECT click FROM products WHERE META().id = $1’

If you know document key use KV ops. Still some reason need to use N1QL (Further filtering, join, aggregates etc) use as USE KEYS avoid index, indexscan

SELECT click FROM products USE KEYS $1