Skip to content

Plan A4: patch deltas, fewer adb round trips, USB timings; bump gpui-hot - #74

Merged
Bombatomica64 merged 1 commit into
mainfrom
cargo-gpui-speed
Oct 12, 2026
Merged

Bombatomica64 merged 1 commit into
mainfrom
cargo-gpui-speed

Conversation

@Bombatomica64

Copy link
Copy Markdown
Owner
  • Bumps gpui-hot to cargo-gpui 266146c (cargo-gpui#2, merged). That change sends patches as zstd deltas against the previous patch, and does each patch and each delta reload in one adb call. gpui-hot itself is unchanged; the rev keeps the lab in step with the CLI. Only the two gpui-hot source lines change in Cargo.lock.
  • docs/hot-patching-plan.md: a new A4 section, and A1's status now points to it.

Measured on the phone (OnePlus, Android 16; Buttons screen, one-line change):

Before After
Patch push + acknowledgement, tunnel ~1.9 s 0.8–1.7 s
Save → applied, tunnel 3.8–4.1 s 2.7–3.6 s
Reload, tunnel 8.2 s 5.3 s
Patch push + acknowledgement, USB 423 ms 308–342 ms
Reload on the phone (push + restart + aslr), USB 1.80 s 1.29 s
  • The tunnel "after" row used -3 deltas (0.32 MB). The final -9 (0.10 MB) ran through the tunnel only while another job saturated the server, so its timings are noted in A4 as skewed, not tabled.
  • For USB, the device commands ran through the laptop's own adb; the patches were built here against the app's aslr. The end-to-end USB figure (~2.2 s per patch) is an estimate, as A4 says.

🤖 Generated with Claude Code

gpui-hot moves to cargo-gpui 266146c (cargo-gpui#2), which sends patches as
deltas against the previous patch and does patches and reloads in one adb
call each. A4 records the numbers through the tunnel and over USB.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Bombatomica64
Bombatomica64 merged commit cc67d0b into main Oct 12, 2026
2 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-12T16:06:46.437676Z 8f003e6 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant