Re:Linux with “memory folios”: a 7% performance boost when c...
by rwmj on Tuesday June 15, 2021 @06:01AM
(#27513138)
Didn't perf work? What difficulties did you encounter?
Re:Linux with “memory folios”: a 7% performance boost when c...
by bayindirh on Tuesday June 15, 2021 @07:26AM
(#27513717)
Used perf record for getting CPU efficiency numbers, and it worked very well, however to be able to reliably trace the code, I had to compile it in debug mode with no optimizations, and run with a single thread. That combination increased the execution time considerably.
Some of the Matrix and solver code coming from Eigen is heavily optimized for SIMD operations and using it with -O0 is just painful.
Moreover, I had to verify its memory sanity and used Valgrind for that. Using a full size problem meant it had to churn for days to finish execution.
Having deadlines doesn't always help in this stuff.
Re:Linux with “memory folios”: a 7% performance boost when c...
by mhh__ on Tuesday June 15, 2021 @11:21AM
(#27516776)
I found perf pretty crummy compared to vTune and even vTune is not fantastic at scale.
Re:Linux with “memory folios”: a 7% performance boost when c...
by bayindirh on Tuesday June 15, 2021 @11:46AM
(#27517153)
I think perf and valgrind is a fantastic combination. While valgrind has a big overhead, it can make a lot of things visible without instrumenting the code.
I also think Perf is phenomenal for its scope. It's showing performance metrics of the code without any processor dependency and instrumentation.
If you're using a few optimized libraries and designed your code for high-speed parallel execution, the compiled thing becomes almost impossible to trace in a practical manner.