I tried with simple curiosity.
same sim but ‘Bgeo’ and ‘bgeo.sc’, respectively.

bgeo.sc
: long cache time
: but small cache size

bgeo
: very short cache time
: but cache size too big batter sc


However, when I import the file, the viewer does not know the difference at all,
and the spreadsheet has the same properties.

What is the difference between the two extensions?
Is there any information I can refer to?

Greeting.
Please check mark's post here:
https://www.sidefx.com/forum/topic/37510/?page=1#post-171095 [sidefx.com]

Nima
Greeting.
Please check mark's post here:
https://www.sidefx.com/forum/topic/37510/?page=1#post-171095 [www.sidefx.com]

What use case would we use compressed "bgeo.sc" over regular bgeo? What information is bgeo.sc lacking?

mannyw

Nima
Greeting.
Please check mark's post here:
https://www.sidefx.com/forum/topic/37510/?page=1#post-171095 [www.sidefx.com]

What use case would we use compressed "bgeo.sc" over regular bgeo? What information is bgeo.sc lacking?

It's not lacking any info, it's a lossless compression similar to zip, which you can also do using bgeo.gz
The aim is to get lower size cache at the expense of slight compression time cost
Having smaller files can also mean faster network transfer that can compensate for compression time, etc

tamte
The aim is to get lower size cache at the expense of slight compression time cost
Having smaller files can also mean faster network transfer that can compensate for compression time, etc

I would guess in most "production" scenarios (for lack of a better word), with centralized storage it will be just like you said. .sc compression on modern CPUs is so negligible compared to everything else involved. One will see the benefits even on smaller scale projects.