couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <p...@hammant.org>
Subject Re: Contract Dev Help
Date Sat, 13 Feb 2016 11:44:39 GMT
Have you tried recreating your setup for a test-harness to try to isolate
the problem?   Use the same deploy script on a fresh DigitalOcean machine -
load it up with docs via curl, try to run your typical queries on in ...
(etc)

On Fri, Feb 12, 2016 at 6:06 PM, Jeff Charette <iomatix@yahoo.com.invalid>
wrote:

> Hi everyone,
>
> Not sure if this is the right place to ask, but we are running CouchDB in
> a production environment and are having serious performance issues on only
> 7000 documents.  I am looking for someone I can pay to take a look, as even
> after 6 years of Couchdb experience I am at my wits end as to what the
> issue is. I’m happy to copy and paste multiple verbose logs, but I believe
> in the end we may need someone with a bit more experience to take a look.
>
> We are using the changes feed with event source for syncing approximately
> 300 devices and are crashing a 16GB 8 core instance on Digital ocean.
> Beam.smp seams to eat all the memory over a 24 hour period.  Any help or
> guidance would be greatly appreciated.
>
> Best,
>
>
> Jeff Charette | Principal
> We Are Charette
> web / identity / packaging
>
> w  wearecharette.com <http://wearecharette.com/>
>
> IRS CIRCULAR 230:  Unless explicitly stated to the contrary, this
> communication (including any attachments) is not intended or written to be
> used, and cannot be used, for the purpose of (i) avoiding penalties under
> the Internal Revenue Code or (ii) promoting, marketing, or recommending to
> another party any transaction or matter addressed herein.
>
> CONFIDENTIALITY:  This email and any attachments may be confidential
> and/or privileged and are therefore protected against copying, use,
> disclosure or distribution.  If you are not the intended recipient, please
> notify us immediately by replying to the sender and double deleting this
> copy and the reply from your system.
>
>
>

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