Skip to content

add mobench support to ProveKit main#429

Closed
dcbuild3r wants to merge 2 commits into
mainfrom
dcbuild3r/main-mobench-fixtures
Closed

add mobench support to ProveKit main#429
dcbuild3r wants to merge 2 commits into
mainfrom
dcbuild3r/main-mobench-fixtures

Conversation

@dcbuild3r

@dcbuild3r dcbuild3r commented Apr 30, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Summary

  • add main-based mobench fixtures for passport, OPRF, and P-256 bigcurve
  • run BrowserStack triad profile across Vivo Y21, Pixel 7, S24 and iOS fallback triad
  • fix Android prove timing so fixture clone/setup is outside the measured prove span
  • use jemalloc as the Android fallback allocator under the native C FFI allocator
  • harden Android incomplete-fixture reporting with timeout/build/kill-evidence fields

Android mobench fix note

The previous failing run was https://github.com/worldfnd/provekit/actions/runs/26007468825. The missing Vivo Y21 monolithic cell did not recover a BrowserStack session payload or summary.json; available artifacts only show the BrowserStack fetch timeout after 7200s for build c943753d95fd0b34f5775aa0a3bc6ff58cbcc3ca. I grepped the recovered Android artifacts and job log for lowmemorykiller, Process * was killed, oom_reaper, SIGKILL, and abnormal signal text; there was no hit because BrowserStack did not return the killed session logs for that cell.

Before/failure memory from that run:

  • Vivo Y21 OPRF: 328 MB process peak, 10.061s
  • Vivo Y21 fragmented age check: 1187 MB process peak, 65.342s
  • Vivo Y21 monolithic age check: no row; BrowserStack timeout/no summary
  • S24 OPRF: 426 MB process peak, 2.809s

What changed:

  • Android and iOS now use the same semantic boundary for prove benches: per-iteration fixture setup happens before the measured closure, and profile_phase("prove") wraps only the prover entry point. Previously prepared.clone() ran inside profile_phase("prove"), so clone cost and peak memory were charged to proving.
  • Android native C FFI fallback allocation now routes through jemalloc instead of Bionic malloc when no host callback/mmap allocator is active.
  • If BrowserStack returns no summary, failure.json now records attempts, fetch timeout seconds, build id, and any LMK/OOM/SIGKILL lines recovered from attempt/device logs.

After numbers: pending the fresh BrowserStack rerun on this commit.

Validation

  • cargo fmt --all
  • cargo test -p bench-mobile --lib
  • cargo test -p bench-mobile --test examples_smoke
  • cargo test -p bench-mobile --test passport_smoke
  • cargo check -p provekit-ffi --target aarch64-linux-android with NDK 26.1 aarch64-linux-android34-clang
  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/mobile-bench-reusable.yml")'
  • git diff --check

@dcbuild3r dcbuild3r mentioned this pull request Apr 30, 2026
Closed
@dcbuild3r

dcbuild3r commented Apr 30, 2026 •
edited by github-actions Bot
Loading

Copy link
Copy Markdown
Collaborator Author

Mobench Benchmark Results

IOS — iPhone 14 (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
oprf-prove 1096.2 1074.8 1117.7 1096.2 1117.7 8.994s 32.55 MB 206.95 MB

2 iterations · 1 warmup · avg is primary metric

IOS — iPhone 16 Pro Max (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
oprf-prove 766.6 758.1 775.2 766.6 775.2 6.728s 10.95 MB 362.28 MB

2 iterations · 1 warmup · avg is primary metric

Note: memory growth excludes warmup/baseline retained before the measured iteration.

IOS — iPhone SE 2022 (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
oprf-prove 1085.4 1085.3 1085.6 1085.4 1085.6 8.972s 33.48 MB 209.44 MB

2 iterations · 1 warmup · avg is primary metric

IOS — iPhone 14 (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-complete-age-check-prove 7771.6 6654.0 8889.1 7771.6 8889.1 56.069s 487.56 MB 1220.12 MB

2 iterations · 1 warmup · avg is primary metric

IOS — iPhone 16 Pro Max (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-complete-age-check-prove 4498.7 4483.9 4513.5 4498.7 4513.5 39.866s 376.08 MB 1594.42 MB

2 iterations · 1 warmup · avg is primary metric

Note: memory growth excludes warmup/baseline retained before the measured iteration.

IOS — iPhone SE 2022 (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-complete-age-check-prove 7443.1 7381.1 7505.0 7443.1 7505.0 60.507s 494.86 MB 1104.30 MB

2 iterations · 1 warmup · avg is primary metric

IOS — iPhone 14 (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-fragmented-age-check-prove 6597.5 6570.0 6625.1 6597.5 6625.1 56.877s 264.30 MB 845.34 MB

2 iterations · 1 warmup · avg is primary metric

IOS — iPhone 16 Pro Max (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-fragmented-age-check-prove 4750.6 4696.1 4805.1 4750.6 4805.1 43.049s 150.95 MB 1042.44 MB

2 iterations · 1 warmup · avg is primary metric

Note: memory growth excludes warmup/baseline retained before the measured iteration.

IOS — iPhone SE 2022 (iOS unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-fragmented-age-check-prove 7053.2 6873.9 7232.6 7053.2 7232.6 61.323s 265.72 MB 851.73 MB

2 iterations · 1 warmup · avg is primary metric

Ios Sina Plot

ios Sina plot

ANDROID — Google Pixel 7 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
oprf-prove 3900.2 3857.8 3942.5 3900.2 3942.5 23.036s 18.23 MB 237.57 MB

2 iterations · 1 warmup · avg is primary metric

ANDROID — Samsung Galaxy M32 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
oprf-prove 6680.8 6436.0 6925.5 6680.8 6925.5 45.282s — 352.76 MB

2 iterations · 1 warmup · avg is primary metric

ANDROID — Samsung Galaxy S24 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
oprf-prove 2724.7 2687.8 2761.6 2724.7 2761.6 19.315s 89.95 MB 488.93 MB

2 iterations · 1 warmup · avg is primary metric

Note: memory growth excludes warmup/baseline retained before the measured iteration.

ANDROID — Google Pixel 7 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-complete-age-check-prove 19856.0 17330.0 22382.0 19856.0 22382.0 127.408s 304.69 MB 980.12 MB

1 iterations · 0 warmup · avg is primary metric

ANDROID — Samsung Galaxy M32 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-complete-age-check-prove 28921.2 27840.2 30002.1 28921.2 30002.1 205.414s 365.05 MB 1220.69 MB

1 iterations · 0 warmup · avg is primary metric

ANDROID — Samsung Galaxy S24 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-complete-age-check-prove 11250.0 10828.9 11671.1 11250.0 11671.1 93.310s 376.77 MB 1157.10 MB

2 iterations · 1 warmup · avg is primary metric

ANDROID — Google Pixel 7 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-fragmented-age-check-prove 26237.3 23605.0 28869.5 26237.3 28869.5 149.220s 217.21 MB 789.64 MB

2 iterations · 1 warmup · avg is primary metric

ANDROID — Samsung Galaxy M32 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-fragmented-age-check-prove 40628.7 40074.6 41182.8 40628.7 41182.8 274.451s 284.89 MB 859.60 MB

1 iterations · 0 warmup · avg is primary metric

ANDROID — Samsung Galaxy S24 (Android unknown)

Benchmark Avg ms Best Worst Median P95 CPU total Peak growth Process peak
passport-fragmented-age-check-prove 14516.4 14336.0 14696.8 14516.4 14696.8 109.112s 202.75 MB 929.28 MB

2 iterations · 1 warmup · avg is primary metric

Note: memory growth excludes warmup/baseline retained before the measured iteration.

Android Sina Plot

android Sina plot

Posted by mobench at 2026-05-25 13:13 UTC

@dcbuild3r dcbuild3r changed the title Run main-based mobench fixtures on low-end devices add mobench support to ProveKit main May 1, 2026
@dcbuild3r dcbuild3r changed the base branch from dcbuild3r/main-mobench-v0137 to main May 3, 2026 07:52
@github-actions

github-actions Bot commented May 3, 2026 •
edited
Loading

Copy link
Copy Markdown

CSP benchmarks

Metric Value
Workflow status [PASS] success
Commit 2f03218b2f00
Run #26368378820
Circuits benchmarked 21
Iterations averaged per circuit 3

Prover time, peak RSS, peak heap, and verifier time are arithmetic means across the iterations. Peak heap comes from the largest peak memory entry in provekit-cli prove's tracing output; peak RSS is reported by /usr/bin/time -v (max-resident-set-size).

No baseline available yet — deltas will appear once this workflow has produced at least one successful main run.

Results
Circuit Constraints Witnesses Prover time Peak RSS Peak heap Verifier time Proof size PKP size
ecdsa_p256 143,282 258,158 2.96 s 262 MB 225 MB 340 ms 2.78 MB 810 KB
keccak_1024 822,870 1,543,366 6.35 s 985 MB 953 MB 837 ms 3.15 MB 6.07 MB
keccak_128 163,058 313,707 2.10 s 274 MB 242 MB 360 ms 2.79 MB 1.22 MB
keccak_2048 1,575,606 2,945,822 11.78 s 1.81 GB 1.80 GB 1.42 s 3.28 MB 12.36 MB
keccak_256 256,206 487,012 2.30 s 331 MB 291 MB 410 ms 2.86 MB 1.97 MB
keccak_512 445,094 839,130 3.60 s 604 MB 509 MB 550 ms 2.98 MB 3.40 MB
poseidon2_12 479 563 347 ms 24.44 MB 14.69 MB 100 ms 1024 KB 436 KB
poseidon2_16 556 719 350 ms 24.71 MB 14.88 MB 100 ms 1.04 MB 530 KB
poseidon2_2 231 278 340 ms 23.50 MB 14.11 MB 100 ms 1.01 MB 108 KB
poseidon2_4 529 535 347 ms 23.78 MB 14.31 MB 100 ms 1.04 MB 31.67 KB
poseidon2_8 363 423 343 ms 24.58 MB 14.50 MB 100 ms 1.04 MB 365 KB
poseidon_12 504 524 350 ms 24.66 MB 14.69 MB 100 ms 1.03 MB 410 KB
poseidon_16 609 633 353 ms 24.71 MB 14.97 MB 103 ms 1020 KB 536 KB
poseidon_2 240 249 340 ms 23.36 MB 14.02 MB 100 ms 1.06 MB 53.79 KB
poseidon_4 297 309 343 ms 23.93 MB 14.31 MB 100 ms 1.05 MB 210 KB
poseidon_8 402 418 343 ms 23.83 MB 14.50 MB 100 ms 1.05 MB 305 KB
sha256_1024 196,940 339,764 2.17 s 309 MB 273 MB 410 ms 2.77 MB 1.86 MB
sha256_128 46,398 80,974 1.08 s 100 MB 83.67 MB 260 ms 2.53 MB 516 KB
sha256_2048 345,399 612,724 3.56 s 548 MB 483 MB 593 ms 2.99 MB 3.13 MB
sha256_256 67,904 117,944 1.37 s 152 MB 131 MB 290 ms 2.65 MB 712 KB
sha256_512 110,916 191,884 1.48 s 181 MB 158 MB 320 ms 2.68 MB 1.12 MB

@dcbuild3r dcbuild3r marked this pull request as ready for review May 3, 2026 22:11
Bisht13
Bisht13 requested changes May 4, 2026
View reviewed changes
Comment thread bench-mobile/fixtures/complete_age_check/Prover.toml Outdated
@@ -0,0 +1,24 @@
dg1 = [60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 48, 55, 48, 49, 48, 49, 60, 60, 51, 50, 48, 49, 48, 49, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 60, 0, 0]

@Bisht13 Bisht13 May 4, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you keep the creation and usage of artifacts inside the workflow itself? That way we'd not need to duplicate toml files and push compiled JSON circuits as well.

@dcbuild3r dcbuild3r May 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in f08820c4: the compiled JSON fixtures and duplicated Prover.toml files are removed from bench-mobile. CI and the BrowserStack reusable workflow now install Noir, run bench-mobile/scripts/generate-fixtures.sh, and build.rs copies the generated noir-examples/*/target/*.json artifacts into OUT_DIR for embedding.

Comment thread bench-mobile/src/bin/uniffi-bindgen.rs Outdated
@@ -0,0 +1,3 @@
fn main() {
uniffi::uniffi_bindgen_main()

@Bisht13 Bisht13 May 4, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use our own FFI crate?

@dcbuild3r dcbuild3r May 4, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which one is that, I could probably do this, but might need to refactor mobench, can you share the link to the crate?

@Bisht13 Bisht13 May 6, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here you go: https://github.com/worldfnd/provekit/tree/main/tooling/provekit-ffi

@dcbuild3r dcbuild3r May 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in f08820c4: bench-mobile now depends on provekit-ffi and uses a new provekit_ffi::in_process helper for prepare/prove/verify. I kept the tiny uniffi-bindgen binary because mobench still expects a UniFFI bindgen entrypoint for mobile runner generation; the ProveKit FFI crate itself remains the proving integration point.

@Bisht13

Bisht13 commented May 4, 2026

Copy link
Copy Markdown
Collaborator

Mobench Benchmark Results

Branch: dcbuild3r/main-mobench-fixtures Base: main Head: ac224d5efd607b645dc7faf502fee3113d74df4e Mobench: provekit-mobench-v0.1.40-ios-readiness (worldcoin/mobile-bench-rs tag) Profile: release, fixtures: passport / OPRF / P256 bigcurve

CI evidence:

iOS device status

iPhone 7 was requested first. BrowserStack rejected it before execution with BROWSERSTACK_NO_DEVICE_FOUND_WITH_REQUESTED_CRITERIA for { device: "iPhone 7", os_version: "1[2-9]" }. The workflow then fell back to iPhone SE 2020-16, which completed all three fixtures.

Device Function Samples Warmup Wall mean / iter Wall total CPU median / iter CPU total CPU / wall Peak growth Process peak
iPhone SE 2020 bench_mobile::bench_passport_complete_age_check_prove 1 0 168.743s 168.743s 207.701s 207.701s 123.1% 1237.19 MB 1272.06 MB
iPhone SE 2020 bench_mobile::bench_oprf_prove 2 1 1.565s 3.131s 6.083s 12.166s 388.6% 100.30 MB 265.55 MB
iPhone SE 2020 bench_mobile::bench_p256_bigcurve_prove 2 1 3.666s 7.332s 12.071s 24.142s 329.3% 253.25 MB 421.77 MB

Android Vivo Y21

Device Function Samples Warmup Wall mean / iter Wall total CPU median / iter CPU total CPU / wall Peak growth Process peak
Vivo Y21 bench_mobile::bench_passport_complete_age_check_prove 1 0 3083.097s 3083.097s 3424.207s 3424.207s 111.1% 1500.10 MB 1613.01 MB
Vivo Y21 bench_mobile::bench_oprf_prove 2 1 10.376s 20.752s 28.638s 57.277s 276.0% 23.11 MB 330.80 MB
Vivo Y21 bench_mobile::bench_p256_bigcurve_prove 2 1 29.105s 58.210s 63.372s 126.745s 217.7% 40.57 MB 576.11 MB
Posted manually from the fork CI run because the workflow token cannot update comments on worldfnd/provekit from dcbuild3r/provekit.

Can we add mid and high tier devices for Android and iOS as well for benchmarking?

@dcbuild3r ChatGPT Codex Connector

dcbuild3r commented May 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Pushed f08820c4 with the review follow-ups:

  • mobile artifacts are generated in CI/BrowserStack workflows instead of checked into bench-mobile
  • bench-mobile now uses provekit-ffi for the in-process prepare/prove/verify path
  • automatic PR mobench runs now use the triad profile, covering low/current, mid-tier, and flagship Android/iOS devices
  • iOS triad uses the schedulable low-tier fallback (iPhone SE 2020-16) plus iPhone 15-17 and iPhone 16 Pro-18, so the low-tier iPhone 7 scheduling limitation does not collapse the whole triad run

I’m waiting for the pushed commit’s GitHub workflows to materialize so the BrowserStack run can execute through repo secrets.

@dcbuild3r dcbuild3r force-pushed the dcbuild3r/main-mobench-fixtures branch from 9a7cd1a to f08820c Compare May 11, 2026 15:50
@dcbuild3r dcbuild3r added the bench Run mobile benchmarks on PRs label May 11, 2026 — with ChatGPT Codex Connector
@dcbuild3r dcbuild3r added bench Run mobile benchmarks on PRs and removed bench Run mobile benchmarks on PRs labels May 14, 2026
@dcbuild3r dcbuild3r added bench Run mobile benchmarks on PRs and removed bench Run mobile benchmarks on PRs labels May 15, 2026
@dcbuild3r dcbuild3r removed the bench Run mobile benchmarks on PRs label May 15, 2026
@dcbuild3r dcbuild3r mentioned this pull request May 18, 2026
Closed
@dcbuild3r

dcbuild3r commented May 29, 2026

Copy link
Copy Markdown
Collaborator Author

Latest mobile benchmark numbers

Source: Mobile Bench PR Auto run 26368378239 on dcbuild3r/main-mobench-fixtures at e14fa60b.
Mobench version: 0.1.42. Artifact summaries report 2 measured runs per function/device plus 1 warmup run.

iOS

Benchmark Device Runs Warmup Mean/run Median p95 Min Max Wall total CPU median/run CPU total CPU/wall Peak growth Peak memory Process peak
OPRF iPhone 16 Pro Max 2 1 766.622ms 766.622ms 775.181ms 758.064ms 775.181ms 1.533s 3.364s 6.728s 438.8% 10.95 MB 10.95 MB 362.28 MB
OPRF iPhone 14 2 1 1.096s 1.096s 1.118s 1.075s 1.118s 2.192s 4.497s 8.994s 410.2% 32.55 MB 32.55 MB 206.95 MB
OPRF iPhone SE 2022 2 1 1.085s 1.085s 1.086s 1.085s 1.086s 2.171s 4.486s 8.972s 413.3% 33.48 MB 33.48 MB 209.44 MB
Passport fragmented iPhone 16 Pro Max 2 1 4.751s 4.751s 4.805s 4.696s 4.805s 9.501s 21.524s 43.049s 453.1% 150.95 MB 150.95 MB 1042.44 MB
Passport fragmented iPhone 14 2 1 6.598s 6.598s 6.625s 6.570s 6.625s 13.195s 28.438s 56.877s 431.0% 264.30 MB 264.30 MB 845.34 MB
Passport fragmented iPhone SE 2022 2 1 7.053s 7.053s 7.233s 6.874s 7.233s 14.106s 30.661s 61.323s 434.7% 265.72 MB 265.72 MB 851.73 MB
Passport complete iPhone 16 Pro Max 2 1 4.499s 4.499s 4.514s 4.484s 4.514s 8.997s 19.933s 39.866s 443.1% 376.08 MB 376.08 MB 1594.42 MB
Passport complete iPhone 14 2 1 7.772s 7.772s 8.889s 6.654s 8.889s 15.543s 28.034s 56.069s 360.7% 487.56 MB 487.56 MB 1220.12 MB
Passport complete iPhone SE 2022 2 1 7.443s 7.443s 7.505s 7.381s 7.505s 14.886s 30.253s 60.507s 406.5% 494.86 MB 494.86 MB 1104.30 MB

Android

Benchmark Device Runs Warmup Mean/run Median p95 Min Max Wall total CPU median/run CPU total CPU/wall Peak growth Peak memory Process peak
OPRF Samsung Galaxy S24 2 1 2.725s 2.725s 2.762s 2.688s 2.762s 5.449s 9.657s 19.315s 354.4% 89.95 MB 89.95 MB 488.93 MB
OPRF Google Pixel 7 2 1 3.900s 3.900s 3.943s 3.858s 3.943s 7.800s 11.518s 23.036s 295.3% 18.23 MB 18.23 MB 237.57 MB
OPRF Samsung Galaxy M32 2 1 6.681s 6.681s 6.926s 6.436s 6.926s 13.362s 22.641s 45.282s 338.9% n/a n/a 352.76 MB
Passport fragmented Samsung Galaxy S24 2 1 14.516s 14.516s 14.697s 14.336s 14.697s 29.033s 54.556s 109.112s 375.8% 202.75 MB 202.75 MB 929.28 MB
Passport fragmented Google Pixel 7 2 1 26.237s 26.237s 28.870s 23.605s 28.870s 52.475s 74.610s 149.220s 284.4% 217.21 MB 217.21 MB 789.64 MB
Passport fragmented Samsung Galaxy M32 2 1 40.629s 40.629s 41.183s 40.075s 41.183s 81.257s 137.225s 274.451s 337.8% 284.89 MB 284.89 MB 859.60 MB
Passport complete Samsung Galaxy S24 2 1 11.250s 11.250s 11.671s 10.829s 11.671s 22.500s 46.655s 93.310s 414.7% 376.77 MB 376.77 MB 1157.10 MB
Passport complete Google Pixel 7 2 1 19.856s 19.856s 22.382s 17.330s 22.382s 39.712s 63.704s 127.408s 320.8% 304.69 MB 304.69 MB 980.12 MB
Passport complete Samsung Galaxy M32 2 1 28.921s 28.921s 30.002s 27.840s 30.002s 57.842s 102.707s 205.414s 355.1% 365.05 MB 365.05 MB 1220.69 MB

Memory growth is the benchmark-reported peak growth above baseline; process peak is the reported process RSS peak.

This was referenced Jun 3, 2026
Open
Open
@dcbuild3r ChatGPT Codex Connector

dcbuild3r commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator Author

Closed in favor of the replacement PR using the new dcbuilder/* branch naming:

Previous CI / benchmark runs for this PR head:

Latest benchmark numbers were reposted on #450: #450 (comment)

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

Reviewers

@Bisht13 Bisht13 Bisht13 requested changes

Assignees

No one assigned

Labels

bench Run mobile benchmarks on PRs

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@dcbuild3r @Bisht13