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

Don't needlessly allocate in Rocket code #26

Closed
wants to merge 1 commit into from
Closed

Don't needlessly allocate in Rocket code #26

wants to merge 1 commit into from

Conversation

SergioBenitez
Copy link
Contributor

No description provided.

@SergioBenitez
Copy link
Contributor Author

Just wanted to show the potential change here. Feel free to implement it if you'd like. :)

@kiliankoe
Copy link
Contributor

Makes sense! 🙈

Any possible improvements should definitely be added, I'm all for adding this change.

@tbrand
Copy link
Collaborator

tbrand commented May 9, 2017

Any possible improvements should definitely be added

Absolutely💯
Thanks @SergioBenitez !!!

@kiliankoe kiliankoe mentioned this pull request May 9, 2017
@SergioBenitez
Copy link
Contributor Author

SergioBenitez commented Jun 16, 2017

Have the benchmarks been rerun with this? I've run the benchmarks locally, and I see timing on the order of Iron/Nickel, not the 2.5x worse value shown in the image.

@kiliankoe
Copy link
Contributor

Others have noticed a certain discrepancy regarding rocket's stats as well, but I don't think anybody knows why it differs. On my machine it's definitely comparable to iron and nickel as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants