feat: add human-readable formatting to EXPLAIN ANALYZE metrics #18689

[T2MIX]

Which issue does this PR close?

• Closes Minor enhancements to EXPLAIN ANALYZE output formatting #18689

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[2010YOUY01]

This PR is well structured and tested, thank you!

The explain analyze format looks much nicer now

> explain analyze
select *
from generate_series(10000000) as t1(v1)
where v1 % 2 = 0;
+-------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| plan_type         | plan                                                                                                                                                                                         |
+-------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Plan with Metrics | ProjectionExec: expr=[value@0 as v1], metrics=[output_rows=5.00 M, elapsed_compute=148.99µs, output_bytes=76.3 MB]                                                                           |
|                   |   FilterExec: value@0 % 2 = 0, metrics=[output_rows=5.00 M, elapsed_compute=30.53ms, output_bytes=76.3 MB, selectivity=50% (5.00 M/10.00 M)]                                                 |
|                   |     RepartitionExec: partitioning=RoundRobinBatch(14), input_partitions=1, metrics=[output_rows=10.00 M, elapsed_compute=598.09µs, output_bytes=76.3 MB]                                     |
|                   |       LazyMemoryExec: partitions=1, batch_generators=[generate_series: start=0, end=10000000, batch_size=8192], metrics=[output_rows=10.00 M, elapsed_compute=10.25ms, output_bytes=76.3 MB] |
|                   |                                                                                                                                                                                              |
+-------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row(s) fetched.
Elapsed 0.018 seconds.

[Copilot]

Pull Request Overview

This PR adds human-readable formatting to EXPLAIN ANALYZE metrics to improve readability by displaying large numbers with K, M, B, T suffixes and durations with appropriate time units (ns, µs, ms, s).

Key Changes

• Added human_readable_count() and human_readable_duration() utility functions for formatting numeric values and time durations
• Updated metric display implementations (Count, Time, PruningMetrics, RatioMetrics, Gauge) to use the new formatting functions
• Added comprehensive test coverage for the new formatting functions

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.

File	Description
datafusion/execution/src/memory_pool/mod.rs	Added human_readable_count() and human_readable_duration() utility functions with tests
datafusion/physical-plan/src/metrics/value.rs	Updated Display implementations for Count, Time, PruningMetrics, RatioMetrics, and Gauge types to use human-readable formatting; added comprehensive tests
datafusion/core/tests/physical_optimizer/filter_pushdown/mod.rs	Updated test assertion to expect human-readable format in output (99872 → 99.87 K)
Cargo.lock	Standard dependency version updates

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[martin-g]

Shouldn't this be displayed as 100.0 K ? With one decimal place ?

[martin-g]

You need to round it first to make it consistent (i.e. 99999 -> 100.0 K):

Suggested change

	if value >= 100.0 {
	let rounded = (value * 100.0).round() / 100.0;
	if rounded >= 100.0 {

[2010YOUY01]

Good point, let's leave it to an optional follow-up.

[2010YOUY01]

Thanks again @T2MIX and @martin-g