-
Notifications
You must be signed in to change notification settings - Fork 323
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
Follow up improvements to Date_Time_Formatter
#7875
Conversation
a0e8034
to
9bbaab9
Compare
Date_Time_Formatter
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.
one slight question but looks good.
distribution/lib/Standard/Base/0.0.0-dev/src/Internal/Time/Format/Analyzer.enso
Outdated
Show resolved
Hide resolved
Added a benchmark (to Exploratory Benchmarks, so it will not be run by CI by default, I don't think it's important enough to run it, but IMO worth keeping in repo). Raw results
Re-creating the formatter at each invocation (default if you call something like In comparison, using We should indeed try adding an LRU cache for the formats. Results with shorter warmup (more CI ready)
|
Benchmarks after implementing the cache Raw results
Adding the cache was definitely worth it - on this example we are about 400x faster than before! After implementing the cache all timings are on par between ~4-11ms. |
Pull Request Description
Data_Formatter.parse
useValue_Type
#7866Important Notes
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
./run ide build
.