chore(query): use num_cpu as default_max_storage_io_requests

[zhang2014]

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/

Summary

chore(query): use num_cpu as default_max_storage_io_requests

Closes #issue

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
databend	⬜️ Ignored (Inspect)			Mar 14, 2023 at 3:17AM (UTC)

[mergify]

This pull request's title is not fulfill the requirements. @zhang2014 please update it 🙏.

Valid format:

fix(query): fix group by string bug
  ^         ^---------------------^
  |         |
  |         +-> Summary in present tense.
  |
  +-------> Type: rfc, feat, fix, refactor, ci, docs, chore

Valid types:

• rfc: this PR proposes a new RFC
• feat: this PR introduces a new feature to the codebase
• fix: this PR patches a bug in codebase
• refactor: this PR changes the code base without new features or bugfix
• ci: this PR changes build/testing/ci steps
• docs: this PR changes the documents or websites
• chore: this PR only has small changes that no need to record

[zhang2014]

We should recommend user unset max_storage_io_requests in the change log. CC: @PsiACE @soyeric128

[soyeric128]

I don't get it. Is it about the setting max_storage_io_requests? Under what circumstances the setting needs a reset?

[zhang2014]

I don't get it. Is it about the setting max_storage_io_requests? Under what circumstances the setting needs a reset?

The user may have set this setting in a previous version. we might recommend that users unset this setting in the change log.