shatejas commented on PR #14076: URL: https://github.com/apache/lucene/pull/14076#issuecomment-2566719988
> I may have overstated my point, I didn’t test it directly. My main concern is that the advice applies for the entire duration of the merge. Since the vector copy occurs at the start and represents only a small portion of the total merge time, I believe using prefetch instead of modifying the advice would be more suitable. Prefetch would allow us to fully control the readahead behavior. On a high level this makes a lot of sense to me. Since we can control the offset and the length in prefetch, it wouldn't be as aggressive as sequential advice and the impact of other parts like search would not be as much in theory. Thanks @jimczi for the explanation. I may take a stab at prefetch solution -- 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: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
