Files
hyperframes/packages
Miguel Angel Simon Sierra a831836dbb perf(studio): commit a group drag in one request
Dragging N elements cost N writes and 9 reads for a three-element group: each
member fetched the composition's parse to preflight, fetched it again to
resolve its tween, then wrote the file on its own round trip. Every one of
those writes re-read, re-parsed and re-serialized the whole composition.

Three changes, same behaviour:

- The parse endpoint shares an in-flight request per file, so callers asking
  for the same composition at the same moment get one request. Only
  overlapping calls share — the entry is dropped as soon as it settles, so a
  read after a write still gets a fresh parse.
- The group preflight runs its members together instead of one at a time. A
  preflight writes nothing, so there is nothing to order.
- Members' mutations are queued and sent as one batch write. Anything that
  re-reads the file flushes the queue first, so a member resolving a shared or
  stale tween never reads a composition missing writes it is about to build
  on. The batch carries each member's runtime patch, and only the last one
  re-renders.

A three-element group drag now issues 2 reads and 1 write, down from 9 and 3.
2026-08-09 19:41:52 -04:00
..
2026-08-09 03:14:27 -07:00
2026-08-09 03:14:27 -07:00
2026-08-09 03:14:27 -07:00
2026-08-09 03:14:27 -07:00
2026-08-09 03:14:27 -07:00
2026-08-09 03:14:27 -07:00
2026-08-09 03:14:27 -07:00