The purpose of these benchmarks is to illustrate that even though opqit may help to reduce compile times and ultimately reduce coupling in your software, it does not come without cost.

Wrapping native iterators in opaque_iterators will have a detrimental effect on performance. So it may be wise to avoid using them in performance-critical code.

I only ran tests on Windows, but I don't see how the general trend would be any different on another O.S. The benchmarks application is in the opqit repository, though, if you would like to try for yourself.

MinGW g++ 4.2.1

MinGW 4.2.1

Microsoft Visual C++ 2009

Visual C++ 2009


Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.