couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Cottlehuber <d...@muse.net.nz>
Subject Re: Running a dev instance of Couch
Date Wed, 18 Apr 2012 16:49:14 GMT
On 18 April 2012 18:33, Mark Hahn <mark@hahnca.com> wrote:
> I recommend that you duplicate the server.  On amazon that takes only
> minutes.  Then release is a simple rcp command.
>
> This is the simplest and safest solution.

Depending on what impact you are trying to avoid, and how big your
current app is, you might just need a second DB on the same instance.
You should not often need to restart couch.

Next stage would be a 2nd instance on the same server (quickest
approach is likely to either build from source with a modified
./configure --....). Unless you're already running into IO limits
while building views or under load this is likely sufficient.

Finally as Mark suggests segregated hosts will reduce the the wallet
as fast as it will avoid cross-couch performance issues. But you will
have the LAN in between your instances then.

A+
Dave

Mime
View raw message