couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <>
Subject Re: What is the purpose of reduce_limit setting
Date Tue, 11 Dec 2012 08:34:13 GMT
"Fix it" is a bit subjective. Its basically a way to signal when you
probably have a reduce function that's misbehaving. The reduce_limit
setting puts an upper limit on the rate at which reduce values can grow as
they are calculated. Its coarse and not super duper awesome but helps avoid
most people understand what's going wrong when they first start using

The only downside to setting reduce_limit=false is that if your reduce
function misbehaves then your view updates will get exponentially slower
and more resource hungry as the view size grows. If you're sufficiently
experienced with reductions and can manage to avoid that situation then
there's no reason to not remove the limit.

If however you do remove the limit then you just have to remember that if
things go south on a view build with a reduce, its probably a bad reduce.

On Tue, Dec 11, 2012 at 2:27 AM, Dmitriy Fot <> wrote:

> Hi everybody,
> I am having hard time finding a concrete answer on question:
> What is the benefit or drawback of setting reduce_limit=false?
> I see this setting in one of the existing deployments and wonder if I want
> to fix it.
> Dmitriy Fot
> ---------------------------------

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