When running the following simple HashAgg-based query on a TPCH-table - Lineitem with 6Billion rows on a 10 node setup (with a single partition to disable any possible spilling to disk)
the runtime increased from 7.378 sec to 11.323 sec [reported by the JDBC client].
To disable spill-to-disk in Drill-1.11.0, the drill-override.conf was modified to
A separate run was done for both scenarios with the planner.width.max_per_node=10 and profiled with YourKit.
Image snippets are attached, indicating the hotspots in both builds:
Drill 1.10.0 :