Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates
 74.125.46.28 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=hVcSK2GbGY75DFbZp5c1Ay1qwI3KEFgfizIT+4ge1DF0uxRGcZOIqbIjLLvNEEvrM4
         lbHe+37JIWzC6yWyQl4VxlFYnGuXhXqU8/iskwfi75/WloZAml8SaRdS+Qs06/nXgoN5
         UCmQODfeCpUFCngSVzRhhPGwQ+MQs+B5dK0rE=
MIME-Version: 1.0
Sender: jchris@gmail.com
In-Reply-To: <23569FFD-1C28-4EF9-8F30-7ADF4B8F22FC@gmail.com>
References: <e282921e0905041508t5d534e62xda338e98822f2659@mail.gmail.com>
	 <23569FFD-1C28-4EF9-8F30-7ADF4B8F22FC@gmail.com>
Date: Mon, 4 May 2009 15:33:16 -0700
Message-ID: <e282921e0905041533w2a93ec8bh25a1ef0bfd1970e8@mail.gmail.com>
Subject: Re: reduce_limit error
From: Chris Anderson <jchris@apache.org>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, May 4, 2009 at 3:23 PM, Adam Kocoloski <adam.kocoloski@gmail.com> w=
rote:
> Thanks for the note, Chris. It might be nice if we could figure out a way
> not to print "wazzup" N*1000 times when the test suite runs :-) =A0Other =
than
> that, cool! =A0Should make support a good bit easier.
>

Yes, that's an interesting side effect of Erlang's dump everything
crash reporting. I'm not sure what to do about that, but a more
general fix could be handy.

Maybe it'd be worth it in this particular case to convert to an
exit(normal) after sending the error message out to linked processes.

> Adam
>
> On May 4, 2009, at 6:08 PM, Chris Anderson wrote:
>
>> Devs,
>>
>> I'm checking in a patch that should cut down on the number of mailing
>> list questions asking why a particular reduce function is hella slow.
>> Essentially the patch throws an error if the reduce function return
>> value is not at least half the size of the values array that was
>> passed in. (The check is skipped if the size is below a fixed amount,
>> 200 bytes for now).
>>
>> I expect this heuristic will need fine tuning. Ideally we'd never
>> raise the error on "good" reduces, and always raise it on
>> "ill-conceived" ones. If you hit the error on a reduce that seems like
>> it should be considered good, please ping the list so we have an
>> opportunity to fine-tune.
>>
>> There is a config option:
>>
>> [query_server_config]
>> reduce_limit =3D true
>>
>> changing this to false will revert to the old behavior. Ideally very
>> few applications will require this config change, so if you find
>> yourself changing this setting, it's a sign you should mail the list.
>>
>> --
>> Chris Anderson
>> http://jchrisa.net
>> http://couch.io
>
>


--=20
Chris Anderson
http://jchrisa.net
http://couch.io