Log which FS is used in DuckDB as debug by AdamGS · Pull Request #6821 · vortex-data/vortex

AdamGS · 2026-03-06T13:56:55Z

This log is currently just noisy in benchmarks, I remember that's was the thing we agreed to do

Signed-off-by: Adam Gutglick <adam@spiraldb.com>

codspeed-hq · 2026-03-06T14:11:19Z

Merging this PR will improve performance by 26.53%

⚡ 3 improved benchmarks
✅ 391 untouched benchmarks
⏩ 2052 skipped benchmarks¹

	Mode	Benchmark	`BASE`	`HEAD`	Efficiency
⚡	Simulation	`take_map[(0.1, 1.0)]`	4.2 ms	3.5 ms	+19.43%
⚡	Simulation	`take_map[(0.1, 0.1)]`	1,007.5 µs	903.3 µs	+11.53%
⚡	Simulation	`take_map[(0.1, 0.5)]`	2.6 ms	2 ms	+26.53%

_{Comparing adamg/debug-log-resolved-fs (f198dc3) with develop (5d6a3c8)²}

2052 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
No successful run was found on develop (b1c5926) during the generation of this report, so 5d6a3c8 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

Log which FS is used in DuckDB as debug

f198dc3

Signed-off-by: Adam Gutglick <adam@spiraldb.com>

AdamGS requested review from a10y and gatesn March 6, 2026 13:56

AdamGS added the changelog/chore A trivial change label Mar 6, 2026

a10y approved these changes Mar 6, 2026

View reviewed changes

AdamGS merged commit fd0f661 into develop Mar 6, 2026
47 of 51 checks passed

AdamGS deleted the adamg/debug-log-resolved-fs branch March 6, 2026 14:20