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 table size feasibility constraints to the planner (for Redshift) #377

Open
geoffxy opened this issue Nov 20, 2023 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@geoffxy
Copy link
Member

geoffxy commented Nov 20, 2023

Redshift dc2.large instances have a hard storage size limit, unlike Aurora and Athena. We should consider this during planning to ensure large tables (e.g., the telemetry table) are placed on an appropriately sized instance.

The costs should ensure that dc2.large nodes are avoided when these large tables are in play.

@geoffxy geoffxy added enhancement New feature or request high priority High priority tasks labels Nov 20, 2023
@geoffxy geoffxy self-assigned this Nov 20, 2023
@geoffxy
Copy link
Member Author

geoffxy commented Nov 21, 2023

This might not be imminently needed for the experiment.

@geoffxy geoffxy removed the high priority High priority tasks label Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant