r/cpp_questions • • 2d ago

OPEN Finalizing performance project

So I'm closing up on a project I've been working on for a few months and it involved profiling using performance tools to improve speed ups. My question is, should I include these benchmarks in the final github, or is the whole point really to just show off pure functionality while stating in your resume how you optimized on performance

1 Upvotes

5 comments sorted by

5

u/WorkingReference1127 2d ago

If you're going to advertise yourself as "I wrote X and then improved performance by Y" then my first question is going to be "how did you improve performance?"

1

u/AKostur 2d ago

Depends on what the project is. But I'd say generally, if I'm looking at a project, I care what it does, not what performance improvements happened in the past. I may care if I'm on v1 and v2 is now out, that it has X performance improvement (ie: may be useful in release notes). But just looking at the front page of a project: I don't care.

1

u/herocoding 2d ago

Would be great to see what and how you actually used the tools, what you tried, what went good, what haven't played out well. Would allow to reproduce.

Would also allow you to remember what you have done.

You might also want to port your project to another environment, another hardware - and measure again, as sometimes there could be HW dependencies; other hardware allow e.g. to use different instruction sets.

1

u/KlutzyCompetition937 2d ago

You could add research notes. Phases and benchmarks you did with parameters.

1

u/Discordbothost 1d ago

include a correctness check beside the benchmarks: baseline and optimized versions should get the same input and agree on the result, or on a stated tolerance. otherwise a faster run might just be doing less work. keep that check runnable too.