Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of torsteinkrausework@gmail.com
 designates 209.85.215.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:content-type:content-transfer-encoding;
        b=x8yWaEjlWUBiAPBUBoXx1ytQU55IAJcoz49f2ThYd4vpWMywj1OtpPrgncRO0k+tYu
         mXToSJ3zHSeQf13t7uKPcD3tBk4OWzUzu+3O257YRDJMdUWDB/twsno4HT4WItdF+ozL
         tXy0ZYhgzD19pXcIVnjgVP6XclK/Px3hAQzJo=
MIME-Version: 1.0
Reply-To: tkj@vizrt.com
In-Reply-To: <BANLkTin02r4yVKCPwbdqYUoJfbf=gyRzbg@mail.gmail.com>
References: <BANLkTinkF_9=GP2fquiXRAaPAou0z-phuA@mail.gmail.com>
	<E580D97B-FE73-43C7-A51A-58FFF835DD73@supercoders.com.au>
	<BANLkTin02r4yVKCPwbdqYUoJfbf=gyRzbg@mail.gmail.com>
Date: Wed, 25 May 2011 16:53:42 +0800
Message-ID: <BANLkTi=7bXDFUQky2A9PhDWKiL_cEXixWw@mail.gmail.com>
Subject: Re: Does CouchDB support gzip encoding?
From: Torstein Krause Johansen <torsteinkrausework@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi again,

On 25 May 2011 16:10, Torstein Krause Johansen
<torsteinkrausework@gmail.com> wrote:
> On 25 May 2011 15:05, Andrew Stuart (SuperCoders)
> <andrew.stuart@supercoders.com.au> wrote:
>> I put nginx in front of the server as a reverse proxy and configure it t=
o do
>> the GZIP compression.

> But after restarting nginx, it seems like I'm still getting text/plain:
>
> =C2=A0wget =C2=A0--header=3D"Accept-Encoding: gzip" -S -O /dev/null
> "http://localhost:80/memento/ ...
> [..]
> =C2=A0HTTP/1.1 200 OK
> =C2=A0Server: nginx/1.0.1
> =C2=A0Date: Wed, 25 May 2011 08:06:34 GMT
> =C2=A0Content-Type: text/plain;charset=3Dutf-8
> =C2=A0Connection: close
> =C2=A0Vary: Accept-Encoding
> =C2=A0Etag: "8YHQMMO1RSGW6DKQHQDBM8X6L"
> =C2=A0Cache-Control: must-revalidate
>
> What am I missing here?

Mhmm, running the same test with curl instead of wget gave me the
desired results. Odd.

The GET still took ~5.5 seconds, though, even though the amount of
data is 1.1M instead of 14M.

Since the _id is half of the data and I don't really need it; is there
any way (outside of a list which takes too long time for so many rows)
to omit the _id (and key) in the view result? (I need the key when
doing the view "search" so I have to emit it in my map.js).

Cheers,

-Torstein