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

Document Extremem relationship between configuration and memory consumption #53

Open
kdnilsen opened this issue Oct 7, 2020 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@kdnilsen
Copy link
Contributor

kdnilsen commented Oct 7, 2020

The configuration options of Extremem are designed to allow Extremem to mimic the memory workload behavior of broad varieties of real-world applications and services. These workloads are typically characterized in terms of:

  1. allocation rate trends
  2. live memory usage trends
  3. object longevity demographics (e.g. 70% of objects die within 50 ms, additional 20% within 10 s, other 10% within 5 minutes)

If customers have good understandings of their services in terms of memory allocation behaviors, it would be desirable that the documentation of Extremem configuration choices would guide them in selection of the configuration parameters that would cause Extremem to approximately match the memory behavior of their service.

In the absence of this documentation, customers are required to select experimental configuration choices, run Extremem with GC logging enabled, compare the GC log output to the comparable GC log output for their service, and then repeat the experiment with adjustments to the experimental configuration choices, iterating until the observed behavior is sufficiently close to the workload they are trying to model.

@kdnilsen kdnilsen added documentation Improvements or additions to documentation enhancement New feature or request labels Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant