I would like to suggest a small improvement to your benchmarks. It has to do with how your setup threats interception.
Generally interception extension severely degrades any container's performance. (Unity, for example, does not recommended it for new development). I once sent you a PR with removed interception, but you added it back.
If you insist on testing interception, perhaps you could test it as a separate case and load the extension only for interception benchmarks? Right now you are loading it for all tests and slow container down by order of 2 or 3.
This issue affects all containers with support for interception and skews results in favor of containers without the interception support.
I would like to suggest a small improvement to your benchmarks. It has to do with how your setup threats interception.
Generally interception extension severely degrades any container's performance. (Unity, for example, does not recommended it for new development). I once sent you a PR with removed interception, but you added it back.
If you insist on testing interception, perhaps you could test it as a separate case and load the extension only for interception benchmarks? Right now you are loading it for all tests and slow container down by order of 2 or 3.
This issue affects all containers with support for interception and skews results in favor of containers without the interception support.
To demonstrate my point here are few numbers:
This is how for your benchmark setup by default:
and this is benchmark with disabled interception:
The difference is quite significant.