Ji/execute iter more #6852

Performance Regression: -49.88%

❌ 11 regressed benchmarks
✅ 989 untouched benchmarks
⏩ 1466 skipped benchmarks¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

	Mode	Benchmark	`BASE`	`HEAD`	Efficiency
❌	Simulation	`take_map[(0.1, 0.05)]`	777.7 µs	1,153.2 µs	-32.56%
❌	Simulation	`take_map[(0.1, 0.1)]`	933.8 µs	1,119.6 µs	-16.59%
❌	Simulation	`take_map[(0.1, 0.5)]`	2.1 ms	2.7 ms	-21.6%
❌	Simulation	`take_map[(0.1, 1.0)]`	3.7 ms	7.4 ms	-49.88%
❌	Simulation	`decompress[alp_for_bp_f64]`	30.3 ms	37.9 ms	-19.96%
❌	Simulation	`decompress[datetime_for_bp]`	41.7 ms	50.1 ms	-16.8%
❌	Simulation	`alp_rd_decompress_f64`	27.4 ms	35.2 ms	-21.95%
❌	Simulation	`decompress_rd[f32, 100000]`	1.9 ms	2.4 ms	-21.98%
❌	Simulation	`decompress_rd[f32, 10000]`	250 µs	305.8 µs	-18.24%
❌	Simulation	`decompress_rd[f64, 10000]`	247.4 µs	357.9 µs	-30.89%
❌	Simulation	`decompress_rd[f64, 100000]`	2.3 ms	3.3 ms	-31.64%

_{Comparing ji/execute-iter-more (a34d0d8) with develop (e477fa5)}

1466 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. ↩