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

Determine minimal but useful heap setting for JVMs including Kafka, Zookeeper, ... + MongoDB/ElasticSearch #44

Open
cer opened this issue May 20, 2020 · 1 comment
Open

Determine minimal but useful heap setting for JVMs including Kafka, Zookeeper, ... + MongoDB/ElasticSearch #44

cer opened this issue May 20, 2020 · 1 comment
Assignees
@dartartem

Comments

@cer
Copy link
Collaborator

cer commented May 20, 2020

Goal: ensure that the example applications use resources effectively.

This needs to be done for all examples, especially eventuate-*-customers-and-orders
@cer cer changed the title Determine minimal but useful heap setting for JVMs including Kafka and Zookeeper Determine minimal but useful heap setting for JVMs including Kafka, Zookeeper, ... + MongoDB/ElasticSearch May 20, 2020
cer added a commit that referenced this issue May 20, 2020
@cer
#44 Specified smaller heapsize for Kafka and ZK
3f61ac5
@cer
Copy link
Collaborator Author

cer commented May 20, 2020

It might make sense for all Eventuate examples to use an Eventuate java base image that has some small heap defaults - need a separate project in eventuate-foundation to build/publish that image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dartartem dartartem

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cer @dartartem