n
> >
> > - Original Message -
> > From: "Adam Kocoloski"
> > To: "dev@couchdb.apache.org Developers"
> > Sent: Monday, October 22, 2018 5:13:05 PM
> > Subject: Re: Exact definition of a database "active size"
> >
&g
to Adam's definition, which I think is closest to the "former" definition
> in Eric's first post.
>
> -Joan
>
> - Original Message -
> From: "Adam Kocoloski"
> To: "dev@couchdb.apache.org Developers"
> Sent: Monday, October 22, 2018 5
+1 to Adam's definition, which I think is closest to the "former" definition in
Eric's first post.
-Joan
- Original Message -
From: "Adam Kocoloski"
To: "dev@couchdb.apache.org Developers"
Sent: Monday, October 22, 2018 5:13:05 PM
Subject: Re: Exact de
I think sizes.active should be a close approximation of the size of the
database after compaction; i.e. it should be possible to use (sizes.file -
sizes.active) as a way to estimate the number of bytes that can be reclaimed by
compacting that database shard.
Adam
> On Oct 22, 2018, at 4:32
Dear all,
I’d like to hear your opinion on how we should interpret a database attribute
“active size”.
As you surely know we are using three different size attributes in a database
info: file - the size of the database file on disk; external - the uncompressed
size of database contents and
