Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com
 designates 209.85.192.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHdjipKokz6h1DhF-1uGcxRisPRmrMM7yXSAEneUSmodizc3ag@mail.gmail.com>
References: 
 <CAHdjipKokz6h1DhF-1uGcxRisPRmrMM7yXSAEneUSmodizc3ag@mail.gmail.com>
Date: Wed, 27 Nov 2013 08:26:57 +0100
Message-ID: 
 <CAJNb-9oKP02Vp7A6wFHdadnyLD_7aQYvGoHL=m5X5y4ntLu_pA@mail.gmail.com>
Subject: Re: NPM, CouchDB and big attachments
From: Benoit Chesneau <bchesneau@gmail.com>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=bcaec520e60ba8a36704ec238562

--bcaec520e60ba8a36704ec238562
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Nov 27, 2013 at 8:14 AM, Alexander Shorin <kxepal@gmail.com> wrote:

> http://blog.nodejs.org/2013/11/26/npm-post-mortem/
>
> > Move attachments out of CouchDB: Work has begun to move the package
> tarballs out of
> > CouchDB and into Joyent's Manta service. Additionally, MaxCDN has
> generously offered to
> > provide CDN services for npm, once the tarballs are moved out of the
> registry database.
> > This will help improve delivery speed, while dramatically reducing the
> file system I/O load on
> > the CouchDB servers. Work is progressing slowly, because at each stage
> in the plan, we are
> > making sure that current replication users are minimally impacted.
>
> I wonder is it CouchDB non-optimal I/O and/or can 769 issue fix it?
>
> https://issues.apache.org/jira/browse/COUCHDB-769
>
> There is alpha-patch attached. May be it's good time to push it
> forward? What things are left for it?
>
> --
> ,,,^..^,,,
>

I would say a better API internally , I am also interrested to work on that

--bcaec520e60ba8a36704ec238562--