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.

Sign up for GitHub

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

Jump to bottom

Performance issues with __inode() reading fileid #5

Open

chinayangxiaowei opened this issue May 24, 2024 · 0 comments

chinayangxiaowei commented May 24, 2024

The __inode() call is a very large overhead when doing a full search, how will it be optimized?

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