You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Adam Wolff <aw...@gmail.com> on 2009/08/18 21:10:10 UTC
couchdb response times
Hi all,We're moving our app towards production, and we're seeing fairly slow
response times from couchdb. Every request to the db appears to take about
100ms, even for just a plain document. Is this expected? Any hints for
better configuration? We're just running what you get after you do make &&
make install on an amazon ec2 big instance, having apt-got erl. We're
running ubuntu intrepid.
Thanks,
A
Re: couchdb response times
Posted by Paul Carey <pa...@gmail.com>.
If you're using instance storage rather than EBS, you may get better
performance by initializing the disks first. [1]
However, this probably isn't relevant if you're simply retrieving docs
and not writing them as I assume CouchDB returns the response before
writing to the log file.
Paul
[1] http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/instance-storage-using.html
On Tue, Aug 18, 2009 at 8:10 PM, Adam Wolff<aw...@gmail.com> wrote:
> Hi all,We're moving our app towards production, and we're seeing fairly slow
> response times from couchdb. Every request to the db appears to take about
> 100ms, even for just a plain document. Is this expected? Any hints for
> better configuration? We're just running what you get after you do make &&
> make install on an amazon ec2 big instance, having apt-got erl. We're
> running ubuntu intrepid.
>
> Thanks,
> A
>
Re: couchdb response times
Posted by Adam Wolff <aw...@gmail.com>.
ab is cool! thanks paul!
On Wed, Aug 19, 2009 at 3:39 PM, Paul Davis <pa...@gmail.com>wrote:
> Another way to test speed is to use something like the ab command.
> That should give you a quick idea of how fast things are.
>
> Paul
>
> On Wed, Aug 19, 2009 at 6:37 PM, Adam Wolff<aw...@gmail.com> wrote:
> > Thanks for the response.
> > It's interesting, when I measure the time with curl, I'm seeing about
> 20ms
> > response times, which isn't great, but is acceptable:For instance, this
> > command:
> > $ curl -v --trace-time "
> >
> http://localhost:5984/user/_design/user/_view/by_userid?key=%226fb045e80b9111ab60bc8601e00293e4%22
> > "
> > Yields:
> > 11:40:52.826454 * About to connect() to localhost port 5984 (#0)
> > 11:40:52.837283 * Trying 127.0.0.1... connected
> > 11:40:52.838314 * Connected to localhost (127.0.0.1) port 5984 (#0)
> > 11:40:52.840666 > GET
> >
> /user/_design/user/_view/by_userid?key=%226fb045e80b9111ab60bc8601e00293e4%22
> > HTTP/1.1
> > 11:40:52.840666 > User-Agent: curl/7.18.2 (x86_64-pc-linux-gnu)
> > libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8
> > 11:40:52.840666 > Host: localhost:5984
> > 11:40:52.840666 > Accept: */*
> > 11:40:52.840666 >
> > 11:40:52.843581 < HTTP/1.1 200 OK
> > 11:40:52.844149 < Transfer-Encoding: chunked
> > 11:40:52.844704 < Server: CouchDB/0.9.0 (Erlang OTP/R12B)
> > 11:40:52.845263 < Etag: "F0Y4SBYHXAO0ZHWG5HJ82JY76"
> > 11:40:52.845817 < Date: Wed, 19 Aug 2009 22:14:24 GMT
> > 11:40:52.846373 < Content-Type: text/plain;charset=utf-8
> > 11:40:52.846928 < Cache-Control: must-revalidate
> > 11:40:52.847491 <
> > {"total_rows":64,"offset":29,"rows":[...]}
> > 11:40:52.848172 * Connection #0 to host localhost left intact
> > 11:40:52.848241 * Closing connection #0
> >
> > Am I correct in reading this as a 20ms response time? Inside my app, the
> > connection is taking more like 100ms.
> > I'm using apache httpclient to connect to couchdb from my java app. I've
> > verified that the time taken by my JSON tokenizer is nominal -- so a bit
> of
> > a digression -- anyone seeing faster response times from couch within
> java?
> > if so, how?
> >
> > Thanks again,
> > A
> >
> > On Tue, Aug 18, 2009 at 2:44 PM, Dmitry Unkovsky <oil.crayons@gmail.com
> >wrote:
> >
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> To me seems very like a storage issue.
> >> What gives
> >> $iostat -xk -d /dev/sda 1 1000
> >> under some load?
> >> Replace /dev/sda with your device (without number), and particularly
> >> svctm is of interest.
> >>
> >> - --
> >> DU
> >>
> >> 2009/8/18 Paul Davis :
> >> > Maybe check that its not just AWS being generally slow? Other than
> >> > that I can't think of anything at the moment.
> >> >
> >> > On Tue, Aug 18, 2009 at 4:41 PM, Adam Wolff wrote:
> >> >> No, I don't think this is a change, but this is the first time I've
> >> really
> >> >> measured.
> >> >>
> >> >> Hm, maybe it wasn't apt that installed erlang:
> >> >> ubuntu@ip-10-251-206-159:~$ erl -version
> >> >> Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 5.6.3
> >> >>
> >> >> Couch version is 0.9.0
> >> >>
> >> >> Anywhere else to look?
> >> >> A
> >> >>
> >> >> On Tue, Aug 18, 2009 at 1:31 PM, Paul Davis wrote:
> >> >>
> >> >>> Adam,
> >> >>>
> >> >>> What version of Erlang did apt give you? And what version of
> CouchDB?
> >> >>>
> >> >>> If I remember right intrepid might be giving you Erlang 5.5.5 (check
> >> >>> with erl -version) and if so, that's very very bad.
> >> >>>
> >> >>> Also, is this a recent change in response times? For singe docs this
> >> >>> seems quite slow regardless of all that. Not sure on EC2 vs anything
> >> >>> else though.
> >> >>>
> >> >>> Paul Davis
> >> >>>
> >> >>> On Tue, Aug 18, 2009 at 3:10 PM, Adam Wolff wrote:
> >> >>> > Hi all,We're moving our app towards production, and we're seeing
> >> fairly
> >> >>> slow
> >> >>> > response times from couchdb. Every request to the db appears to
> take
> >> >>> about
> >> >>> > 100ms, even for just a plain document. Is this expected? Any hints
> >> for
> >> >>> > better configuration? We're just running what you get after you do
> >> make
> >> >>> &&
> >> >>> > make install on an amazon ec2 big instance, having apt-got erl.
> We're
> >> >>> > running ubuntu intrepid.
> >> >>> >
> >> >>> > Thanks,
> >> >>> > A
> >> >>> >
> >> >>>
> >> >>
> >> >
> >>
> >>
> >>
> >>
> >>
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v1.4.9 (GNU/Linux)
> >>
> >> iEYEARECAAYFAkqLILAACgkQqdN5Ji6VwmffKACeIuKvp2KErNF+uIEq4pCguLfK
> >> 6WgAn1wNSHbjk49q3pa8p98efCq55gDg
> >> =IEIh
> >> -----END PGP SIGNATURE-----
> >>
> >
>
Re: couchdb response times
Posted by Paul Davis <pa...@gmail.com>.
Another way to test speed is to use something like the ab command.
That should give you a quick idea of how fast things are.
Paul
On Wed, Aug 19, 2009 at 6:37 PM, Adam Wolff<aw...@gmail.com> wrote:
> Thanks for the response.
> It's interesting, when I measure the time with curl, I'm seeing about 20ms
> response times, which isn't great, but is acceptable:For instance, this
> command:
> $ curl -v --trace-time "
> http://localhost:5984/user/_design/user/_view/by_userid?key=%226fb045e80b9111ab60bc8601e00293e4%22
> "
> Yields:
> 11:40:52.826454 * About to connect() to localhost port 5984 (#0)
> 11:40:52.837283 * Trying 127.0.0.1... connected
> 11:40:52.838314 * Connected to localhost (127.0.0.1) port 5984 (#0)
> 11:40:52.840666 > GET
> /user/_design/user/_view/by_userid?key=%226fb045e80b9111ab60bc8601e00293e4%22
> HTTP/1.1
> 11:40:52.840666 > User-Agent: curl/7.18.2 (x86_64-pc-linux-gnu)
> libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8
> 11:40:52.840666 > Host: localhost:5984
> 11:40:52.840666 > Accept: */*
> 11:40:52.840666 >
> 11:40:52.843581 < HTTP/1.1 200 OK
> 11:40:52.844149 < Transfer-Encoding: chunked
> 11:40:52.844704 < Server: CouchDB/0.9.0 (Erlang OTP/R12B)
> 11:40:52.845263 < Etag: "F0Y4SBYHXAO0ZHWG5HJ82JY76"
> 11:40:52.845817 < Date: Wed, 19 Aug 2009 22:14:24 GMT
> 11:40:52.846373 < Content-Type: text/plain;charset=utf-8
> 11:40:52.846928 < Cache-Control: must-revalidate
> 11:40:52.847491 <
> {"total_rows":64,"offset":29,"rows":[...]}
> 11:40:52.848172 * Connection #0 to host localhost left intact
> 11:40:52.848241 * Closing connection #0
>
> Am I correct in reading this as a 20ms response time? Inside my app, the
> connection is taking more like 100ms.
> I'm using apache httpclient to connect to couchdb from my java app. I've
> verified that the time taken by my JSON tokenizer is nominal -- so a bit of
> a digression -- anyone seeing faster response times from couch within java?
> if so, how?
>
> Thanks again,
> A
>
> On Tue, Aug 18, 2009 at 2:44 PM, Dmitry Unkovsky <oi...@gmail.com>wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> To me seems very like a storage issue.
>> What gives
>> $iostat -xk -d /dev/sda 1 1000
>> under some load?
>> Replace /dev/sda with your device (without number), and particularly
>> svctm is of interest.
>>
>> - --
>> DU
>>
>> 2009/8/18 Paul Davis :
>> > Maybe check that its not just AWS being generally slow? Other than
>> > that I can't think of anything at the moment.
>> >
>> > On Tue, Aug 18, 2009 at 4:41 PM, Adam Wolff wrote:
>> >> No, I don't think this is a change, but this is the first time I've
>> really
>> >> measured.
>> >>
>> >> Hm, maybe it wasn't apt that installed erlang:
>> >> ubuntu@ip-10-251-206-159:~$ erl -version
>> >> Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 5.6.3
>> >>
>> >> Couch version is 0.9.0
>> >>
>> >> Anywhere else to look?
>> >> A
>> >>
>> >> On Tue, Aug 18, 2009 at 1:31 PM, Paul Davis wrote:
>> >>
>> >>> Adam,
>> >>>
>> >>> What version of Erlang did apt give you? And what version of CouchDB?
>> >>>
>> >>> If I remember right intrepid might be giving you Erlang 5.5.5 (check
>> >>> with erl -version) and if so, that's very very bad.
>> >>>
>> >>> Also, is this a recent change in response times? For singe docs this
>> >>> seems quite slow regardless of all that. Not sure on EC2 vs anything
>> >>> else though.
>> >>>
>> >>> Paul Davis
>> >>>
>> >>> On Tue, Aug 18, 2009 at 3:10 PM, Adam Wolff wrote:
>> >>> > Hi all,We're moving our app towards production, and we're seeing
>> fairly
>> >>> slow
>> >>> > response times from couchdb. Every request to the db appears to take
>> >>> about
>> >>> > 100ms, even for just a plain document. Is this expected? Any hints
>> for
>> >>> > better configuration? We're just running what you get after you do
>> make
>> >>> &&
>> >>> > make install on an amazon ec2 big instance, having apt-got erl. We're
>> >>> > running ubuntu intrepid.
>> >>> >
>> >>> > Thanks,
>> >>> > A
>> >>> >
>> >>>
>> >>
>> >
>>
>>
>>
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (GNU/Linux)
>>
>> iEYEARECAAYFAkqLILAACgkQqdN5Ji6VwmffKACeIuKvp2KErNF+uIEq4pCguLfK
>> 6WgAn1wNSHbjk49q3pa8p98efCq55gDg
>> =IEIh
>> -----END PGP SIGNATURE-----
>>
>
Re: couchdb response times
Posted by Jason Anderson <jl...@gmail.com>.
I'm not sure of the default setting but I'd make sure the Nagle
algorithm is disabled
see HttpConnectionParams#setTcpNoDelay()
On Wed, Aug 19, 2009 at 3:37 PM, Adam Wolff<aw...@gmail.com> wrote:
> Thanks for the response.
> It's interesting, when I measure the time with curl, I'm seeing about 20ms
> response times, which isn't great, but is acceptable:For instance, this
> command:
> $ curl -v --trace-time "
> http://localhost:5984/user/_design/user/_view/by_userid?key=%226fb045e80b9111ab60bc8601e00293e4%22
> "
> Yields:
> 11:40:52.826454 * About to connect() to localhost port 5984 (#0)
> 11:40:52.837283 * Trying 127.0.0.1... connected
> 11:40:52.838314 * Connected to localhost (127.0.0.1) port 5984 (#0)
> 11:40:52.840666 > GET
> /user/_design/user/_view/by_userid?key=%226fb045e80b9111ab60bc8601e00293e4%22
> HTTP/1.1
> 11:40:52.840666 > User-Agent: curl/7.18.2 (x86_64-pc-linux-gnu)
> libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8
> 11:40:52.840666 > Host: localhost:5984
> 11:40:52.840666 > Accept: */*
> 11:40:52.840666 >
> 11:40:52.843581 < HTTP/1.1 200 OK
> 11:40:52.844149 < Transfer-Encoding: chunked
> 11:40:52.844704 < Server: CouchDB/0.9.0 (Erlang OTP/R12B)
> 11:40:52.845263 < Etag: "F0Y4SBYHXAO0ZHWG5HJ82JY76"
> 11:40:52.845817 < Date: Wed, 19 Aug 2009 22:14:24 GMT
> 11:40:52.846373 < Content-Type: text/plain;charset=utf-8
> 11:40:52.846928 < Cache-Control: must-revalidate
> 11:40:52.847491 <
> {"total_rows":64,"offset":29,"rows":[...]}
> 11:40:52.848172 * Connection #0 to host localhost left intact
> 11:40:52.848241 * Closing connection #0
>
> Am I correct in reading this as a 20ms response time? Inside my app, the
> connection is taking more like 100ms.
> I'm using apache httpclient to connect to couchdb from my java app. I've
> verified that the time taken by my JSON tokenizer is nominal -- so a bit of
> a digression -- anyone seeing faster response times from couch within java?
> if so, how?
>
> Thanks again,
> A
>
> On Tue, Aug 18, 2009 at 2:44 PM, Dmitry Unkovsky <oi...@gmail.com>wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> To me seems very like a storage issue.
>> What gives
>> $iostat -xk -d /dev/sda 1 1000
>> under some load?
>> Replace /dev/sda with your device (without number), and particularly
>> svctm is of interest.
>>
>> - --
>> DU
>>
>> 2009/8/18 Paul Davis :
>> > Maybe check that its not just AWS being generally slow? Other than
>> > that I can't think of anything at the moment.
>> >
>> > On Tue, Aug 18, 2009 at 4:41 PM, Adam Wolff wrote:
>> >> No, I don't think this is a change, but this is the first time I've
>> really
>> >> measured.
>> >>
>> >> Hm, maybe it wasn't apt that installed erlang:
>> >> ubuntu@ip-10-251-206-159:~$ erl -version
>> >> Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 5.6.3
>> >>
>> >> Couch version is 0.9.0
>> >>
>> >> Anywhere else to look?
>> >> A
>> >>
>> >> On Tue, Aug 18, 2009 at 1:31 PM, Paul Davis wrote:
>> >>
>> >>> Adam,
>> >>>
>> >>> What version of Erlang did apt give you? And what version of CouchDB?
>> >>>
>> >>> If I remember right intrepid might be giving you Erlang 5.5.5 (check
>> >>> with erl -version) and if so, that's very very bad.
>> >>>
>> >>> Also, is this a recent change in response times? For singe docs this
>> >>> seems quite slow regardless of all that. Not sure on EC2 vs anything
>> >>> else though.
>> >>>
>> >>> Paul Davis
>> >>>
>> >>> On Tue, Aug 18, 2009 at 3:10 PM, Adam Wolff wrote:
>> >>> > Hi all,We're moving our app towards production, and we're seeing
>> fairly
>> >>> slow
>> >>> > response times from couchdb. Every request to the db appears to take
>> >>> about
>> >>> > 100ms, even for just a plain document. Is this expected? Any hints
>> for
>> >>> > better configuration? We're just running what you get after you do
>> make
>> >>> &&
>> >>> > make install on an amazon ec2 big instance, having apt-got erl. We're
>> >>> > running ubuntu intrepid.
>> >>> >
>> >>> > Thanks,
>> >>> > A
>> >>> >
>> >>>
>> >>
>> >
>>
>>
>>
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (GNU/Linux)
>>
>> iEYEARECAAYFAkqLILAACgkQqdN5Ji6VwmffKACeIuKvp2KErNF+uIEq4pCguLfK
>> 6WgAn1wNSHbjk49q3pa8p98efCq55gDg
>> =IEIh
>> -----END PGP SIGNATURE-----
>>
>
Re: couchdb response times
Posted by Adam Wolff <aw...@gmail.com>.
Thanks for the response.
It's interesting, when I measure the time with curl, I'm seeing about 20ms
response times, which isn't great, but is acceptable:For instance, this
command:
$ curl -v --trace-time "
http://localhost:5984/user/_design/user/_view/by_userid?key=%226fb045e80b9111ab60bc8601e00293e4%22
"
Yields:
11:40:52.826454 * About to connect() to localhost port 5984 (#0)
11:40:52.837283 * Trying 127.0.0.1... connected
11:40:52.838314 * Connected to localhost (127.0.0.1) port 5984 (#0)
11:40:52.840666 > GET
/user/_design/user/_view/by_userid?key=%226fb045e80b9111ab60bc8601e00293e4%22
HTTP/1.1
11:40:52.840666 > User-Agent: curl/7.18.2 (x86_64-pc-linux-gnu)
libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8
11:40:52.840666 > Host: localhost:5984
11:40:52.840666 > Accept: */*
11:40:52.840666 >
11:40:52.843581 < HTTP/1.1 200 OK
11:40:52.844149 < Transfer-Encoding: chunked
11:40:52.844704 < Server: CouchDB/0.9.0 (Erlang OTP/R12B)
11:40:52.845263 < Etag: "F0Y4SBYHXAO0ZHWG5HJ82JY76"
11:40:52.845817 < Date: Wed, 19 Aug 2009 22:14:24 GMT
11:40:52.846373 < Content-Type: text/plain;charset=utf-8
11:40:52.846928 < Cache-Control: must-revalidate
11:40:52.847491 <
{"total_rows":64,"offset":29,"rows":[...]}
11:40:52.848172 * Connection #0 to host localhost left intact
11:40:52.848241 * Closing connection #0
Am I correct in reading this as a 20ms response time? Inside my app, the
connection is taking more like 100ms.
I'm using apache httpclient to connect to couchdb from my java app. I've
verified that the time taken by my JSON tokenizer is nominal -- so a bit of
a digression -- anyone seeing faster response times from couch within java?
if so, how?
Thanks again,
A
On Tue, Aug 18, 2009 at 2:44 PM, Dmitry Unkovsky <oi...@gmail.com>wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> To me seems very like a storage issue.
> What gives
> $iostat -xk -d /dev/sda 1 1000
> under some load?
> Replace /dev/sda with your device (without number), and particularly
> svctm is of interest.
>
> - --
> DU
>
> 2009/8/18 Paul Davis :
> > Maybe check that its not just AWS being generally slow? Other than
> > that I can't think of anything at the moment.
> >
> > On Tue, Aug 18, 2009 at 4:41 PM, Adam Wolff wrote:
> >> No, I don't think this is a change, but this is the first time I've
> really
> >> measured.
> >>
> >> Hm, maybe it wasn't apt that installed erlang:
> >> ubuntu@ip-10-251-206-159:~$ erl -version
> >> Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 5.6.3
> >>
> >> Couch version is 0.9.0
> >>
> >> Anywhere else to look?
> >> A
> >>
> >> On Tue, Aug 18, 2009 at 1:31 PM, Paul Davis wrote:
> >>
> >>> Adam,
> >>>
> >>> What version of Erlang did apt give you? And what version of CouchDB?
> >>>
> >>> If I remember right intrepid might be giving you Erlang 5.5.5 (check
> >>> with erl -version) and if so, that's very very bad.
> >>>
> >>> Also, is this a recent change in response times? For singe docs this
> >>> seems quite slow regardless of all that. Not sure on EC2 vs anything
> >>> else though.
> >>>
> >>> Paul Davis
> >>>
> >>> On Tue, Aug 18, 2009 at 3:10 PM, Adam Wolff wrote:
> >>> > Hi all,We're moving our app towards production, and we're seeing
> fairly
> >>> slow
> >>> > response times from couchdb. Every request to the db appears to take
> >>> about
> >>> > 100ms, even for just a plain document. Is this expected? Any hints
> for
> >>> > better configuration? We're just running what you get after you do
> make
> >>> &&
> >>> > make install on an amazon ec2 big instance, having apt-got erl. We're
> >>> > running ubuntu intrepid.
> >>> >
> >>> > Thanks,
> >>> > A
> >>> >
> >>>
> >>
> >
>
>
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkqLILAACgkQqdN5Ji6VwmffKACeIuKvp2KErNF+uIEq4pCguLfK
> 6WgAn1wNSHbjk49q3pa8p98efCq55gDg
> =IEIh
> -----END PGP SIGNATURE-----
>
Re: couchdb response times
Posted by Dmitry Unkovsky <oi...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To me seems very like a storage issue.
What gives
$iostat -xk -d /dev/sda 1 1000
under some load?
Replace /dev/sda with your device (without number), and particularly
svctm is of interest.
- --
DU
2009/8/18 Paul Davis :
> Maybe check that its not just AWS being generally slow? Other than
> that I can't think of anything at the moment.
>
> On Tue, Aug 18, 2009 at 4:41 PM, Adam Wolff wrote:
>> No, I don't think this is a change, but this is the first time I've really
>> measured.
>>
>> Hm, maybe it wasn't apt that installed erlang:
>> ubuntu@ip-10-251-206-159:~$ erl -version
>> Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 5.6.3
>>
>> Couch version is 0.9.0
>>
>> Anywhere else to look?
>> A
>>
>> On Tue, Aug 18, 2009 at 1:31 PM, Paul Davis wrote:
>>
>>> Adam,
>>>
>>> What version of Erlang did apt give you? And what version of CouchDB?
>>>
>>> If I remember right intrepid might be giving you Erlang 5.5.5 (check
>>> with erl -version) and if so, that's very very bad.
>>>
>>> Also, is this a recent change in response times? For singe docs this
>>> seems quite slow regardless of all that. Not sure on EC2 vs anything
>>> else though.
>>>
>>> Paul Davis
>>>
>>> On Tue, Aug 18, 2009 at 3:10 PM, Adam Wolff wrote:
>>> > Hi all,We're moving our app towards production, and we're seeing fairly
>>> slow
>>> > response times from couchdb. Every request to the db appears to take
>>> about
>>> > 100ms, even for just a plain document. Is this expected? Any hints for
>>> > better configuration? We're just running what you get after you do make
>>> &&
>>> > make install on an amazon ec2 big instance, having apt-got erl. We're
>>> > running ubuntu intrepid.
>>> >
>>> > Thanks,
>>> > A
>>> >
>>>
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqLILAACgkQqdN5Ji6VwmffKACeIuKvp2KErNF+uIEq4pCguLfK
6WgAn1wNSHbjk49q3pa8p98efCq55gDg
=IEIh
-----END PGP SIGNATURE-----
Re: couchdb response times
Posted by Paul Davis <pa...@gmail.com>.
Maybe check that its not just AWS being generally slow? Other than
that I can't think of anything at the moment.
On Tue, Aug 18, 2009 at 4:41 PM, Adam Wolff<aw...@gmail.com> wrote:
> No, I don't think this is a change, but this is the first time I've really
> measured.
>
> Hm, maybe it wasn't apt that installed erlang:
> ubuntu@ip-10-251-206-159:~$ erl -version
> Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 5.6.3
>
> Couch version is 0.9.0
>
> Anywhere else to look?
> A
>
> On Tue, Aug 18, 2009 at 1:31 PM, Paul Davis <pa...@gmail.com>wrote:
>
>> Adam,
>>
>> What version of Erlang did apt give you? And what version of CouchDB?
>>
>> If I remember right intrepid might be giving you Erlang 5.5.5 (check
>> with erl -version) and if so, that's very very bad.
>>
>> Also, is this a recent change in response times? For singe docs this
>> seems quite slow regardless of all that. Not sure on EC2 vs anything
>> else though.
>>
>> Paul Davis
>>
>> On Tue, Aug 18, 2009 at 3:10 PM, Adam Wolff<aw...@gmail.com> wrote:
>> > Hi all,We're moving our app towards production, and we're seeing fairly
>> slow
>> > response times from couchdb. Every request to the db appears to take
>> about
>> > 100ms, even for just a plain document. Is this expected? Any hints for
>> > better configuration? We're just running what you get after you do make
>> &&
>> > make install on an amazon ec2 big instance, having apt-got erl. We're
>> > running ubuntu intrepid.
>> >
>> > Thanks,
>> > A
>> >
>>
>
Re: couchdb response times
Posted by Adam Wolff <aw...@gmail.com>.
No, I don't think this is a change, but this is the first time I've really
measured.
Hm, maybe it wasn't apt that installed erlang:
ubuntu@ip-10-251-206-159:~$ erl -version
Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 5.6.3
Couch version is 0.9.0
Anywhere else to look?
A
On Tue, Aug 18, 2009 at 1:31 PM, Paul Davis <pa...@gmail.com>wrote:
> Adam,
>
> What version of Erlang did apt give you? And what version of CouchDB?
>
> If I remember right intrepid might be giving you Erlang 5.5.5 (check
> with erl -version) and if so, that's very very bad.
>
> Also, is this a recent change in response times? For singe docs this
> seems quite slow regardless of all that. Not sure on EC2 vs anything
> else though.
>
> Paul Davis
>
> On Tue, Aug 18, 2009 at 3:10 PM, Adam Wolff<aw...@gmail.com> wrote:
> > Hi all,We're moving our app towards production, and we're seeing fairly
> slow
> > response times from couchdb. Every request to the db appears to take
> about
> > 100ms, even for just a plain document. Is this expected? Any hints for
> > better configuration? We're just running what you get after you do make
> &&
> > make install on an amazon ec2 big instance, having apt-got erl. We're
> > running ubuntu intrepid.
> >
> > Thanks,
> > A
> >
>
Re: couchdb response times
Posted by Paul Davis <pa...@gmail.com>.
Adam,
What version of Erlang did apt give you? And what version of CouchDB?
If I remember right intrepid might be giving you Erlang 5.5.5 (check
with erl -version) and if so, that's very very bad.
Also, is this a recent change in response times? For singe docs this
seems quite slow regardless of all that. Not sure on EC2 vs anything
else though.
Paul Davis
On Tue, Aug 18, 2009 at 3:10 PM, Adam Wolff<aw...@gmail.com> wrote:
> Hi all,We're moving our app towards production, and we're seeing fairly slow
> response times from couchdb. Every request to the db appears to take about
> 100ms, even for just a plain document. Is this expected? Any hints for
> better configuration? We're just running what you get after you do make &&
> make install on an amazon ec2 big instance, having apt-got erl. We're
> running ubuntu intrepid.
>
> Thanks,
> A
>