Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a benchmark test for the object pool #676

Merged
merged 2 commits into from
Jul 28, 2015
Merged

Conversation

codemercenary
Copy link
Contributor

ObjectPool will need to be a performant type. Add a benchmark so we can track its improvement. Current object pool times show ObjectPool as about 4x slower than malloc for flat datatypes, and 2x slower than malloc for types that allocate additional memory. This is clearly an unacceptable situation.

Addresses #674

`ObjectPool` will need to be a performant type.  Add a benchmark so we can track its improvement.  Current object pool times show `ObjectPool` as about 4x slower than `malloc` for flat datatypes, and 2x slower than `malloc` for types that allocate additional memory.  This is clearly an unacceptable situation.
@codemercenary
Copy link
Contributor Author

Current benchmarks:

objpool
basic                                   68.542  ns  100.00%
complex                                 219.18  ns  319.77%
pool_basic                              378.65  ns  552.43%
pool_complex                            383.64  ns  559.71%

gittyupagain pushed a commit that referenced this pull request Jul 28, 2015
Add a benchmark test for the object pool
@gittyupagain gittyupagain merged commit 715e297 into develop Jul 28, 2015
@gittyupagain gittyupagain deleted the feature-bmobjpool branch July 28, 2015 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants