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

Add index row estimation is not fully usable #52085

Closed
tangenta opened this issue Mar 25, 2024 · 0 comments · Fixed by #52086
Closed

Add index row estimation is not fully usable #52085

tangenta opened this issue Mar 25, 2024 · 0 comments · Fixed by #52086

Comments

@tangenta
Copy link
Contributor

Enhancement

According to the add-index test result, wider tables are more likely to encounter bottlenecks at the table reader, and CPU utilization could be very low. #52000 adopts a strategy to determine reader concurrency: it used a statistic cache to estimate average row size of a table, and adjust reader count based on it.

However, statistic cache is not always available. For example, if a table has never executed ANALYZE, there is no data in statistic cache. For large tables, even if we analyze them with a low sample rate, it is still time-consuming.

We should investigate another way to estimate average row size efficiently.

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

Successfully merging a pull request may close this issue.

1 participant