pitrou commented on issue #44084:
URL: https://github.com/apache/arrow/issues/44084#issuecomment-2350920377

   Two potential downsides to this approach:
   1) the size taken by those temporary `ResolvedChunk`s is twice the size of 
indices, hence a bigger CPU cache footprint
   2) there has to be a final "reverse resolution" step where we convert back 
the sorted `ResolvedChunk`s into absolute indices... or we maintain those 
absolute indices along the `ResolvedChunk`, which implies an ever bigger cache 
footprint
   
   Experimenting will tell whether this can be beneficial.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to