Re: new database files not compressed

Hamish Moffatt
2020-09-04T08:07:50Z

On 4/9/20 5:44 am, Zygo Blaxell wrote:
> On Thu, Sep 03, 2020 at 10:53:23PM +1000, Hamish Moffatt wrote:
>
>> I recompiled Firebird with fallocate disabled (it has a fallback for
>> non-linux OSs), and now I have compressed database files.
>>
>> It may be that de-duplication suits my application better anyway. Will
>> compsize tell me how much space is being saved by de-duplication, or is
>> there another way to find out?
> Compsize reports "Uncompressed" and "Referenced" columns. "Uncompressed"
> is the physical size of the uncompressed data (i.e. how many bytes
> you would need to hold all of the extents on disk without compression
> but with dedupe). "Referenced" is the logical size of the data, after
> counting each reference (i.e. how many bytes you would need to hold all
> of the data without compression or dedupe).
>
> The "none" and "zstd" rows will tell you how much dedupe you're getting
> on uncompressed and compressed extents separately.

Great, I have it bees running and I see the deduplication in compsize as
you said.

What is the appropriate place to ask question about bees - here, github
or elsewhere?

I added some files, restarted bees and it ran a deduplication, but then
I added some more files (8 hours ago) and there's been some regularly
logging but the new files haven't been deduplicated.

Hamish