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
8304976: Optimize DateTimeFormatterBuilder.ZoneTextPrinterParser.getTree() #12612
Conversation
👋 Welcome back stsypanov! A progress list of the required criteria for merging this PR into |
@stsypanov The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Benchmarking
|
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a nice fix to me.
test/micro/org/openjdk/bench/java/time/format/ZonedDateTimeFormatterBenchmark.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@stsypanov This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 64 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@naotoj) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@stsypanov |
/sponsor |
Going to push as commit 438c969.
Your commit was automatically rebased without conflicts. |
@naotoj @stsypanov Pushed as commit 438c969. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk17u-dev |
@olivergillespie the backport was successfully created on the branch olivergillespie-backport-438c969b in my personal fork of openjdk/jdk17u-dev. To create a pull request with this backport targeting openjdk/jdk17u-dev:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk17u-dev:
|
When
DateTimeFormatter
is reused we don't need to copyavailableZoneIds
and allocatenonRegionIds
as PrefixTree can be taken from cache. In the related benchmark allocation ofHashSet
takes ~93% of all time, so avoiding it should bring some improvement for cases when we reuseDateTimeFormatter
to parse a string intoZoneDateTime
DateTimeFormatter
is mostly used with one locale, socachedTree
andcachedTreeCI
can have predefined size.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/12612/head:pull/12612
$ git checkout pull/12612
Update a local copy of the PR:
$ git checkout pull/12612
$ git pull https://git.openjdk.org/jdk.git pull/12612/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12612
View PR using the GUI difftool:
$ git pr show -t 12612
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12612.diff