-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustdoc-json: buffer output #93954
rustdoc-json: buffer output #93954
Conversation
@bors r+ rollup=never (perf?) |
📌 Commit ae15822 has been approved by |
⌛ Testing commit ae15822 with merge 8859ab012852ee4bcb88a3deb3abe1b5c7a35794... |
💔 Test failed - checks-actions |
@bors retry |
@aDotInTheVoid: 🔑 Insufficient privileges: not in try users |
@bors retry |
@bors rollup=maybe I don't think this is likely to affect perf in practice, so let's permit rolling it up. |
It only effects perf on the rustdoc json backend, which we currently dont track perf for, but we should |
…askrgr Rollup of 7 pull requests Successful merges: - rust-lang#92902 (Improve the documentation of drain members) - rust-lang#93658 (Stabilize `#[cfg(panic = "...")]`) - rust-lang#93954 (rustdoc-json: buffer output) - rust-lang#93979 (Add debug assertions to validate NUL terminator in c strings) - rust-lang#93990 (pre rust-lang#89862 cleanup) - rust-lang#94006 (Use a `Field` in `ConstraintCategory::ClosureUpvar`) - rust-lang#94086 (Fix ScalarInt to char conversion) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
It turns out we were doing syscalls for each part of the json syntax
Before:
After:
In one benchmark (one struct, almost all time in
std
), this gives ~2x perfr? @CraftSpider
@rustbot modify labels: +A-rustdoc-json +T-rustdoc -A-testsuite