Concurrent performance improvements; add performance settings field; support IgnoreCollisions
#384
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description: This streamlines the concurrent access path.
Link to tracking Issue:
Fixes #377.
Documentation: New section in lightstep/sdk/metric/README.md.
Testing: New test added. New benchmarks added, see below. Results are no change for standard configuration, potential 10% improvement with new option.
Performance claim evaluated by raising the Concurrent test load factor:
Performance after:
Performance before shows each test was substantially slower:
Benchmarks after are about the same as below, using the default, safe configuration.
New benchmarks use the unsafe code path, indicating about a 10% time improvement vs the corresponding benchmark above. Also note one less allocation which is because when ignoring collisions there is no need to copy the original attribute slice.
Benchmarks before: