couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Dionne <>
Subject Re: Bringing automatic compaction into trunk
Date Tue, 16 Aug 2011 12:08:39 GMT

  This is neat, I can definitely see the utility of the approach. I do share the concerns
expressed in other comments with respect to the use of the config file for per db compaction
specs and the use of a compact_loop that waits on config change messages when the ets table
is empty. I don't think it fully takes into account the use case of large numbers of small
dbs and/or some very large dbs interspersed with a lot of mid-size dbs.

  Anyway I like it a lot though I've only read the code for 1/2 and hour or so. I also agree
with others that the code base is reaching a point of being a bit crufty and it might be a
good time with the git migration, etc.. to take a breath and commit to making some of these
OTP compliant changes and design changes we've talked about.



On Aug 15, 2011, at 9:29 PM, Filipe David Manana wrote:

> Developers, users,
> It's been a while now since I opened a Jira ticket for it (
> ).
> I won't describe it here with detail since it's already done in the Jira ticket.
> Unless there are objections, I would like to get this moving soon.
> Thanks
> -- 
> Filipe David Manana,
> "Reasonable men adapt themselves to the world.
>  Unreasonable men adapt the world to themselves.
>  That's why all progress depends on unreasonable men."

View raw message