When I tried replicating the NPM registry on Windows it bluescreened the machine when the Erlang process reached about 1GB. On the plus side, once the machine was rebooted, replication continued past 40GB, though it did begin to slow down at that point. I don't really want the registry, so stopped replicating at that point, but I got the feeling that you could get the full registry onto a Windows CouchDb installation if you stop and restart the CouchDb service when memory consumption gets too high.
Nick On 9 December 2013 09:10, Thor Anker Lange (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842996#comment-13842996] > > Thor Anker Lange commented on COUCHDB-1946: > ------------------------------------------- > > I am seeing the exact same behaviour when reaching 30-40 GB running > CouchDB on Windows (yes, unfortunally I do not have a choice of server OS). > The source start sequence is around 701252. > > Marc, how did you manage to get a complete replica of the npm registry? > > > Trying to replicate NPM grinds to a halt after 40GB > > --------------------------------------------------- > > > > Key: COUCHDB-1946 > > URL: https://issues.apache.org/jira/browse/COUCHDB-1946 > > Project: CouchDB > > Issue Type: Bug > > Components: Database Core > > Reporter: Marc Trudel > > Attachments: couch.log > > > > > > I have been able to replicate the Node.js NPM database until 40G or so, > then I get this: > > https://gist.github.com/stelcheck/7723362 > > I one case I have gotten a flat-out OOM error, but I didn't take a dump > of the log output at the time. > > CentOS6.4 with CouchDB 1.5 (also tried 1.3.1, but to no avail). Also > tried to restart replication from scratch - twice - bot cases stalling at > 40GB. > > > > -- > This message was sent by Atlassian JIRA > (v6.1.4#6159) >
