Deformation things are sometimes more profitable to write in alembic than in bgeo.sc. Transformations are in no way more profitable to write in alembic.
If there is repeating geometry (several repeating packed primitives with the same path), writing them to alembic with separation by the path attribute will fail, and writing in bgeo.sc will be much more optimal.
And in the case of deformation, and in the case of transformation when writing to an alembic, you need to do a hierarchy separation by the path attribute, regardless of what we write: geometry or alembic primitives. Double packing will not happen.
This is not necessary in the case of deformations – memory savings will be about a percent. But it is better to make a breakdown in both cases for a single approach.