couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stanley Iriele <>
Subject Re: Large views and concurrent access
Date Fri, 14 Jun 2013 22:38:48 GMT
I agree caching is always going to be faster when done correctly...if it
were pulling across the wire I would try compressing it because its the
transfer of 1.5 MB that's getting you.

But I guess without knowing the extent of dynamism your require with your
query it possible to split your large view into smaller views that you
could query in clever ways?... Also is that is there a high write to read
ratio?.. It could be fixing the index during this
On Jun 14, 2013 1:52 PM, "Jens Alfke" <> wrote:

> On Jun 14, 2013, at 12:09 PM, mangvlad <> wrote:
> > I guess I can introduce some caching in my node.js layer, but ideally,
> > I would like to "exhaust" my couchdb options first...
> It’s always going to be much faster to cache local objects than to
> download and parse 1.5MB of JSON, no matter how fast the CouchDB server
> gets.
> Consider using conditional GETs, so you’ll get the updated view results if
> they’ve changed, and a simple 304 response if they haven’t.
> —Jens

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message