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

[couchbase] Explicitly configure service quotas (and allow customizat… #4802

Merged
merged 1 commit into from Jan 4, 2022

Conversation

daschl
Copy link
Member

@daschl daschl commented Dec 27, 2021

…ion).

This changeset explicitly configures the service memory quotas to their
documented limits by default. This ensures that if a service is enabled,
it does not consume more memory than absolutely needed. This is important
because some services (like analytics) try to grab memory available which
is good for production but of limited use in a testcontainers setting.

A new API is also added which allows to customize the memory quota for
each service should the test case require more than the minimum (which
for most services is 256MB anyways).

@daschl
Copy link
Member Author

daschl commented Dec 28, 2021

note: I also reformatted the services file since the whitespace wasn't aligned with the other files.

…ion).

This changeset explicitly configures the service memory quotas to their
documented limits by default. This ensures that if a service is enabled,
it does not consume more memory than absolutely needed. This is important
because some services (like analytics) try to grab memory available which
is good for production but of limited use in a testcontainers setting.

A new API is also added which allows to customize the memory quota for
each service should the test case require more than the minimum (which
for most services is 256MB anyways).
Copy link
Member

@kiview kiview left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM in general, see the comment about having the minimum quota values hardcoded. Maybe it is better (for forward and backward compatibility?) to treat those as default, rather than minimum values?

@kiview kiview added this to the next milestone Jan 4, 2022
@kiview kiview merged commit 04d5247 into testcontainers:master Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants