@ifc-lite/cache - Binary cache format for fast model loading
The .ifc-lite format skips re-running the parse + tessellation pipeline on
a warm load: entities, relationships, spatial hierarchy and geometry are
all pre-computed and read back directly. That's where the 5-10x is real.
Properties and quantities are the exception: write() serializes whatever
the store's property/quantity tables already hold. A STEP-parsed
IfcDataStore resolves those lazily on demand and never populates the
tables, so a cache written straight from a STEP parse has EMPTY property
and quantity tables — a restored model queries properties exactly as slow
as a fresh parse, unless the caller separately retains the source buffer
and re-attaches on-demand extraction (see docs/guide/querying.md).
@ifc-lite/cache - Binary cache format for fast model loading
The .ifc-lite format skips re-running the parse + tessellation pipeline on a warm load: entities, relationships, spatial hierarchy and geometry are all pre-computed and read back directly. That's where the 5-10x is real.
Properties and quantities are the exception:
write()serializes whatever the store's property/quantity tables already hold. A STEP-parsedIfcDataStoreresolves those lazily on demand and never populates the tables, so a cache written straight from a STEP parse has EMPTY property and quantity tables — a restored model queries properties exactly as slow as a fresh parse, unless the caller separately retains the source buffer and re-attaches on-demand extraction (seedocs/guide/querying.md).Example