Skip to content

Work preference #6244

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

Open
killme2008 opened this issue Jun 4, 2025 · 0 comments
Open

Work preference #6244

killme2008 opened this issue Jun 4, 2025 · 0 comments
Labels
C-feature Category Features

Comments

@killme2008
Copy link
Contributor

killme2008 commented Jun 4, 2025

What problem does the new feature solve?

By default, GreptimeDB's queries and writes fully utilize resources like CPU.
However, in certain specific scenarios, you might prefer to prioritize real-time writes at the expense of query performance, or vice versa. Therefore, I think we can provide a workPreference option to let users decide:

  • The default value would be balance,
  • with options to choose read or write to indicate specific work preferences.

Once a specific preference is selected, configurations such as concurrency limits and task priorities can be optimized accordingly.

FYI. This feature is useful for standalone or edge scenarios. In cluster versions, workload separation can always be achieved using different node pools.

What does the feature do?

Let user choose the workload preference.

Implementation challenges

No response

@killme2008 killme2008 added the C-feature Category Features label Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category Features
Projects
None yet
Development

No branches or pull requests

1 participant