GH-48957: [Benchmarking] Add temporal type support to benchmarks #48958
+113
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale for this change
The Python benchmark suite was missing coverage for temporal types (date, timestamp, time, duration), making it difficult to check performance of temporal type conversions over time. There was a TODO comment in
convert_builtins.pyfor this.What changes are included in this PR?
benchmarks/common.pyfor date, timestamp, time, and durationconvert_builtins.py,microbenchmarks.py, andarray_ops.pybenchmarks to include temporal typesAre these changes tested?
Tested as follows:
Are there any user-facing changes?
No.