Profile-Guided Optimization (PGO) benchmark results #34
                  
                    
                      zamazan4ik
                    
                  
                
                  started this conversation in
                General
              
            Replies: 1 comment
-
| 
         Great work! Very useful! Thank you so much! 👍 Since the topic is, as you say, not a bug report, I've converted it to a discussion.  | 
  
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I evaluate Profile-Guided Optimization (PGO) performance improvements for applications and libraries (including other JSON parsers) in different software domains - all current results can be found here. According to the tests, PGO helps to improve performance in various software domains. I decided to perform PGO benchmarks on the
actson-rslibrary too since some library users may be interested in improving the library's performance. I did some benchmarks and here are the results.Test environment
actson-rsversion:mainbranch on commit332b8922eb6b3960956902fe80cc031c13f09dd6Benchmark
For benchmark purposes, I use two benchmarks: via
cargo benchand geojson benchmarks.For
cargo benchset of benchmarks, the PGO training phase is done withcargo pgo bench, PGO optimization phase - withcargo pgo optimize bench.For geojson set of benchmarks, I used
run-all.shscript. For the PGO training phase, I used completely the same script but the instrumented binary is built withcargo pgo build, and the number of runs was settled to 1 since there is no need to run more frequently for the training phase in this case.All PGO-related routines are done with cargo-pgo.
All benchmarks are done on the same machine, with the same hardware/software during runs, with the same background "noise" (as much as I can guarantee, of course).
Results
Firstly, here are the results for
cargo bench:Geojson results:
Raw files (
results.jsonfiles) are also saved on my machine - I can share them as well if you are interested.At least in the provided by project benchmarks, there are measurable improvements in many cases. Also, I got the same results for other JSON benchmarks that can be found in the
awesome-pgorepo.Maybe mentioning these results somewhere in the README (or any other user-facing documentation) can be a good idea. Probably you will be interested in integrating building
actson-rswith PGO into your applications - who knows :)Please do not treat the issue as a bug or something like that - it's just a benchmark report.
Beta Was this translation helpful? Give feedback.
All reactions