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.

Sign up for GitHub

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

Jump to bottom

Optimize a bit memory usage of StrimziKafkaContainer #92

Closed
wants to merge 1 commit into from
Closed

Optimize a bit memory usage of StrimziKafkaContainer #92

wants to merge 1 commit into from

Conversation

see-quick
Copy link
Member

This PR tries to solve problems with memory consumption.

##[warning]Free memory is lower than 5%; Currently used: 95.10%
##[warning]Free memory is lower than 5%; Currently used: 95.10%

@see-quick
Optimize a bit memory usage of StrimziKafkaContainer
3dc59a9 
Signed-off-by: see-quick <maros.orsak159@gmail.com>
@see-quick see-quick added this to the 0.108.0 milestone Oct 16, 2024
scholzj
scholzj reviewed Oct 16, 2024
View reviewed changes
Copy link
Member

@scholzj scholzj left a comment

Choose a reason for hiding this comment

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

Do we really want to have change the default here? I think they should be chngeable by the users. but changing it like this could break a lot of things without a clear reason.

@see-quick
Copy link
Member Author

Do we really want to have change the default here? I think they should be chngeable by the users. but changing it like this could break a lot of things without a clear reason.

Yeah, that's reasonable.

@see-quick see-quick closed this Oct 24, 2024
@see-quick see-quick deleted the optmize-kafka-container branch November 6, 2024 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@scholzj scholzj scholzj left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.108.0
Development

Successfully merging this pull request may close these issues.
2 participants
@see-quick @scholzj