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

database node resource sizes available #491

Open
fideloper opened this issue Jul 9, 2024 · 3 comments
Open

database node resource sizes available #491

fideloper opened this issue Jul 9, 2024 · 3 comments

Comments

@fideloper
Copy link

Hi! It looks like there are some minimum database sizes we can choose:

minStorageQuantity = resource.MustParse("1G") //nolint:gochecknoglobals
minCPUQuantity = resource.MustParse("600m") //nolint:gochecknoglobals
minMemQuantity = resource.MustParse("512M") //nolint:gochecknoglobals

minStorageQuantity = resource.MustParse("1G")   //nolint:gochecknoglobals
 minCPUQuantity     = resource.MustParse("600m") //nolint:gochecknoglobals
 minMemQuantity     = resource.MustParse("512M") //nolint:gochecknoglobals

We're hoping to create many, tiny databases (single node, some temporary and some just very small) - our cost planning would prefer to use smaller CPU sizes than 600m.

Our tests showing this working fine for our minimal use case but these minimums are too high. I was curious if these are set for a reason other than stopping us from shooting ourselves in our foot? Is that possible to be overwritten/changed? (Happy to send a PR).

Thanks!

@fideloper fideloper changed the title database size options database node resource sizes available Jul 9, 2024
@recharte
Copy link
Collaborator

recharte commented Jul 10, 2024

Hi @fideloper, thank you for bringing this up.

I'll be totally transparent and say that I don't know why we have these particular limits. These were added as part of a bigger scope of validations in this PR.

To be honest, they seem arbitrary and definitely don't make sense to be shared across the different engine types.
However, we have a ticket (EVEREST-696) that mentions that backups were failing with these minimum resource requirements so there's a chance that unlocking the minimum requirements would lead to more of these issues.

I think this requires more investigation and testing before we can just blindly remove the limits. We'll look into this and report back.

Nonetheless, can you share more details about your use case? Which DB engine(s) are you interested in running and what are the resource limits that fit your use cases?

@fideloper
Copy link
Author

I'm sorry I missed your reply from over a month ago!

Ideally we'd be able to set sizes for both mysql and pgsql, altho we're looking towards MySQL (I have not tested pgsql in smaller sizes like I have with mysql).

We have a use case where we'll have potentially many small databases for non-critical workloads (dev/staging environments). For environments that were more important (and where backups were more important), we'd have larger instance sizes.

@calvinps
Copy link

@recharte ideally we'd like to try out a minimum CPU size of 125m to 250m.

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

No branches or pull requests

3 participants