Hi, Martin. I am the author of Procouch however it is largely vaporware at this time.
I am concluding a semi-forced vacation after a semi-death march :) So I will be working on projects this week, rested and clear-thinking. (CentOS 5 support is also on my to-do list.) Anyway, please submit an issue to the Procouch project indicating what features are more important to you and I will work to get those done first. Thanks! On Fri, Apr 20, 2012 at 12:34 PM, Martin Hewitt <[email protected]> wrote: > Thanks Robert and Dave, that procouch project in particular looks very > interesting, we already do much of what it does in our application anyway, > but moving that into a standalone daemon has a lot of appeal. > > Martin > > -- > Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > > > On Friday, 20 April 2012 at 14:28, Dave Cottlehuber wrote: > >> On 20 April 2012 14:41, Robert Newson <[email protected]> wrote: >> > Yes, it's deliberate. BigCouch (and CouchDB) doesn't typically >> > allocate a lot of memory (though lots of replication jobs would change >> > that). Having lots of RAM is recommended for the OS's disk cache, >> > however. >> > >> > B. >> >> You might be able to use it by pre-heating views, or querying with >> appropriate include_docs. Jason Smith wrote a script to do that for >> CouchDB which you could try. >> >> http://web.archiveorange.com/archive/v/oW6Dz2vTi9LDuZ92hKwy >> https://github.com/iriscouch/procouch/blob/master/lib/view_heater.js >> in https://github.com/iriscouch/procouch >> >> A+ >> Dave >> >> > > -- Iris Couch
