supabase / supabase-flutter / 32373781271

89%

push

github

perf(yet_another_json_isolate): process small payloads inline and large ones on short-lived isolates (#1746)

## What kind of change does this PR introduce?

Performance improvement for `yet_another_json_isolate`, plus a benchmark
to keep it honest. Resolves the copying and serialization overhead of
the long-lived isolate design.

## What is the current behavior?

`YAJsonIsolate` keeps one long-lived isolate per instance and routes
every `decode`/`encode` through it. This has three hidden costs:

- Small payloads pay an isolate messaging round trip that costs more
than parsing them inline.
- Large decoded object graphs are deep-copied back to the calling
isolate, which roughly doubles the work and stalls the main isolate for
up to ~10ms on 5MB payloads.
- Concurrent calls are processed one at a time through a single event
queue.

On top of that, both postgrest and the functions client decode the HTTP
body bytes to a `String` on the main isolate before handing it over.

## What is the new behavior?

The long-lived isolate is gone. The public API is unchanged
(`initialize`/`dispose` are kept as compatibility no-ops with the same
contracts), and internally:

- Payloads estimated below 64KB are processed inline, where the parse
takes well under a millisecond even on slow devices.
- Larger payloads run on a short-lived isolate per call via
`Isolate.run`, whose result is handed back through `Isolate.exit`
without copying. Concurrent calls run in parallel.
- A new `decodeBytes(Uint8List)` API takes HTTP `bodyBytes` directly:
the bytes move to the isolate via `TransferableTypedData` without
copying, and the UTF-8 and JSON decoding steps are fused so the
intermediate string never materializes on the calling isolate. The
postgrest and functions clients now use it.
- `encode` picks its path with a cheap bounded size estimate
(depth-capped, so cyclic input still reaches `jsonEncode`'s own cycle
error on the isolate).

## Benchmarks

A benchmark now lives in `pack... (continued)

57 of 59 new or added lines in 3 files covered. (96.61%)

5908 of 6676 relevant lines covered (88.5%)

4.35 hits per line