-
Notifications
You must be signed in to change notification settings - Fork 25
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
There should be a speed test showing the issue (if any) between compiler optimization and January #420
Comments
gerring
added a commit
to gerring/january
that referenced
this issue
Feb 3, 2020
Closed
gerring
added a commit
to gerring/january
that referenced
this issue
Feb 3, 2020
gerring
added a commit
to gerring/january
that referenced
this issue
Feb 3, 2020
gerring
added a commit
to gerring/january
that referenced
this issue
Feb 3, 2020
I think any benchmark should use JMH. Can you refactor to do that and place it in separate fragment? |
gerring
added a commit
to gerring/january
that referenced
this issue
Feb 3, 2020
gerring
added a commit
to gerring/january
that referenced
this issue
Feb 3, 2020
gerring
added a commit
to gerring/january
that referenced
this issue
Feb 3, 2020
gerring
added a commit
to gerring/january
that referenced
this issue
Feb 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be good to have a speed test to show where the current nD looping under performs against the compiler optimized basic loop. If January is slow then the test could be commented out until the team decides to fix something.
The text was updated successfully, but these errors were encountered: