Reuse port-point output for Pipeline9 node Pf calculations - #2473
Reuse port-point output for Pipeline9 node Pf calculations#2473AnasSarkiz wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Benchmark This PRRun benchmarks by commenting on this PR: Comment Everything after Use Any PR whose title contains |
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Workflow: View run |
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
|
/benchmark --pipeline 9 --dataset srj18 --profile-solvers |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Workflow: View run |
srj18 ResultsProfile Solvers: completed. Comparison tables are included below. Main vs PRDataset: srj18 · Scenarios: 16 · Effort: 1x effort
DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing changes are faster. Previous main run details
Previous main profile details12/16 scenarios solved (4 failed) in 361.4s
PR run details
PR profile comparison12/16 scenarios solved (4 failed) in 361.5s
Workflow: View run |
|
/benchmark --dataset 18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Workflow: View run |
|
@AnasSarkiz you definitely get credit for this fix (100%) but my AI rewrote it and I think it's a bit more understandable #2475 rather than iterate on naming i'm going to merge that PR but this fix credit should go to you |
Summary
Pipeline9 already constructs the port-point output before preparing high-density routing. Reuse that output for each node's Pf calculation instead of rebuilding the complete output for every node.
Validation
207c4191.@tscircuit/fanout-for-pipeline9-fixtures. CI must verify the current head.A prior same-machine SRJ18 sample 6 pair on
f55494c7measured 217.342s to 200.469s end-to-end (7.8% less time), with identical output, ordered DRC findings, 97 existing DRC issues, and 300 vias. This is one sample pair, not a full-suite or current-main performance claim. Benchmark tooling and artifacts are not included.