Big .sbc files

[johny65]

We have a database with 50+ millions of records that when compressed it occupies 4 GB, but we noted that uncompressed it is 120 GB of files, with lot of big collections_xxxx_xxxxxxxxx.sbc files, that are almost empty (lot of 0 bytes). We found an old thread with this information:

.sbc files are used to store relations (edges) between vertexes. In sbc files space is occupied by removed edges reused only if it occupies half of total space to make possible to put all edges related to single vertex in close to each other on the disk.
Could you set parameter sbtreebonsai.freeeSpaceReuseTrigger to 0 and check result ?

Is there a way to "clean" this files in an existent database to reduce its size? We have no success with the mentioned parameter (sbtreebonsai.freeSpaceReuseTrigger). We also found in this page the existence of show holes and compact database commands but only for version 2. What could we do in version 3?

[mdre]

Also, we export / Import database and we get a ~20GB used space after the process, so there are 100GB of waste space.

[johny65]

Some values:

• Original database in version 3.0: 120 GB.
• Exported and imported in 3.0: 20 GB.
• Exported and imported in 3.1: 15 GB.
• Exported and imported in 3.1 with SBTree Bonsai ridbags: 237 GB.

How is this possible?

[andrii0lomakin]

Hi guys, there is exactly the same issue in the bug tracker, we are working on it right now.

[andrii0lomakin]

Sorry, that is an issue created by the customer which uses commercial support. None the less we are working on this problem right now it will be released in 3.1.x and on ward version.

[johny65]

Yes, we are the commercial customer that created the issue 😅. We are now testing the snapshot build you send us. Thank you for your work.

[andrii0lomakin]

OK. :-) Please note that is not the final version, the final version should be faster, my primary concern now is testing of disk space consumption.

[johny65]

I don't see this documented anywhere, but if someone else is affected, version 3.2 solves this.