Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lock the random access if a forward or backward seek is detected #1250

Open
wants to merge 1 commit into
base: uberChannelLimit
Choose a base branch
from

Conversation

arunmahadevan
Copy link

The optimized AUTO_RANDOM mode currently requires a switch to sequential before it can switch to random. The proposed change locks the access pattern to random as soon as a forward or backward seek is detected.

Copy link

google-cla bot commented Sep 13, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

&& consecutiveSequentialCount >= readOptions.getFadviseRequestTrackCount()
&& readOptions.getFadvise() == Fadvise.AUTO_RANDOM;
}

private boolean shouldDetectRandomAccess() {
return !randomAccess
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If already in randomAccess mode there is no need to detect random access.

I do agree that the current logic will not update backwardSeek and forwardSeek if occurredwhen random access was set but I would suggest updating those flags well within fn:updateAccessPattern .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants