You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing this for the history. Maybe these results will be interesting to someone who trying to achieve better performance with xml-rs.
I test Profile-Guided Optimization (PGO) on different kinds of software - the current results are here(with a lot of other PGO-related information). That's why I tried to optimize xml-rs with PGO too.
But as a library author I can't do anything with this information. It's something that end users need to enable.
Actually, you can write a note about this kind of performance improvement for the library somewhere in the documentation (even a note in README is completely ok). In this case, the users will be aware of how to improve performance of the library with this optimization technique even with actual numbers.
Writing this for the history. Maybe these results will be interesting to someone who trying to achieve better performance with
xml-rs
.I test Profile-Guided Optimization (PGO) on different kinds of software - the current results are here(with a lot of other PGO-related information). That's why I tried to optimize
xml-rs
with PGO too.Test setup
My test setup is:
rustc 1.73.0-nightly (180dffba1 2023-08-14)
xml-rs
version:c6331c97ab9f487c9d0bce52c06364116f5e80d2
commit from themaster
branchBenchmarks
As a benchmark, I used built-in into the
xml-rs
crate benchmarks. For PGO optimization I use cargo-pgo.Results
Release:
Release + PGO:
Instrumented:
As you see, PGO allows parsing XML faster.
The text was updated successfully, but these errors were encountered: