Ermouth,
Congratulations with digging out hidden features of CouchDB!
I presume this works with new 2.0 and 1.7 and that these versions now have a
new feature, Caching:)
johs
> On 26. mai 2016, at 22.17, ermouth wrote:
>
> Tested approach, works like a charm )
>
> Surprisingly, it appears that
Tested approach, works like a charm )
Surprisingly, it appears that approach is more suitable not for rendering
pages, but for requests view->list, that respond with hundreds or thousands
of small rows. In those cases I observe sometimes 2 orders of magnitude
gain or even more, ie 300-500ms query
> - a function in a _list of a certain ddoc called directly via the _list
endpint
It‘s called via rewrite. Rewrite decides to call list. If rewrite already
have a result in cache and the result is not too old, rewrite sends results
directly.
If there is no result cached or it‘s too old, rewrite r
Hi Ermouth,
this sounds like a bonus feature of significant value:)
Together with the rewrite function this discovery would keep the couchapp
enthusiasts of the community happy for a looong time, I believe.
If I understand you right,
- a function in a _list of a certain ddoc called directly via
Since JS rewrites landed in 2.0, and I use JS rewrites heavily, I discover
some tricks with the new feature time to time. Despite I use patched 1.6.1
with js rewrites, tricks are suitable for at least single node 2.0 as well.
JS rewrites function runs in the context of a query server instance. QS