Skip to content

Conversation

@google-labs-jules
Copy link

This patch improves the performance of RepartitionExec for hash-based repartitioning by deferring the materialization of RecordBatches. It introduces a PartitionedBatch::Indexed variant, which contains a shared Arc<RecordBatch> and a PrimitiveArray<UInt32Type> of indices. The producer now sends this lightweight enum over the channels, and the take operation is performed by the consumer tasks. This parallelizes the take operation across all output partitions, improving throughput. A memory accounting issue was also fixed by passing the estimated size of the Indexed batch along with the batch, ensuring that the memory pool's grow and shrink operations are symmetric.


PR created automatically by Jules for task 14803450406354175091 started by @Dandandan

This patch improves the performance of `RepartitionExec` for hash-based repartitioning by deferring the materialization of `RecordBatch`es.

Previously, the producer task would perform the expensive `take` operation to create a new `RecordBatch` for each output partition. This serialized a costly operation that is now parallelized.

This patch introduces a `PartitionedBatch::Indexed` variant, which contains a shared `Arc<RecordBatch>` and a `PrimitiveArray<UInt32Type>` of indices. The producer now sends this lightweight enum over the channels, and the `take` operation is performed by the consumer tasks. This parallelizes the `take` operation across all output partitions, improving throughput.

To fix a memory accounting issue that arose from this change, the estimated size of the `Indexed` batch is now passed along with the batch, ensuring that the memory pool's `grow` and `shrink` operations are symmetric.
@google-labs-jules
Copy link
Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant