Make aspnet core benchmark more realistic

[Barsonax]

Currently the aspnet core benchmark resolves just a single scoped instances 3 times per scope. This makes it very easy to design a container that scores high on this specific workload. All one needs to do is use a datastructure thats fast on adding items and fast on returning that item if there is only 1 item. A datastructure such as a singlylinked list or even a simple field could be used for this.

Containers using such a datastructure in this case may seem to be the fastest however given the fact that such a approach does not scale very well it may give the wrong impression.

Just to give you a idea its pretty trivial to make Singularity perform 2x faster on this benchmark by doing this.

I think it would be better if:

• More work is done per scope. Currently there is lots of overhead in creating the scope itself because the actual workload inside the scope itself is very small.
• There are more than 1 scoped instances. This should make it harder to cheese the benchmark with a SinglyLinked list or even a simple field to store the scoped instance.
• These scoped instances are resolved many times to put more pressure on the read performance of the particular datastructure that a given container is using. If this is not changed then the benchmark would favor datastructures that are fast on adding new items.

[danielpalme]

You are right, it would be possible to create an optimized container. But that's always possible in a fixed scenario.

If you like you can change that. I won't invest any time in this benchmark any more (apart from updating the containers from time to time).