Bug 1515968 - Improve documentation around running Java workloads on OpenShift
Summary: Improve documentation around running Java workloads on OpenShift
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.9.0
Assignee: Jim Minter
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-21 17:17 UTC by Jim Minter
Modified: 2021-09-09 12:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-11 17:59:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jim Minter 2017-11-21 17:17:56 UTC
1) Basic principles, available controls and approach (memory requests & limits, k8s QoS, JVM -Xmx and similar options, -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap, -XX:MaxRAMFraction, JAVA|MAVEN|GRADLE|*_OPTIONS)

2) Recommended settings for builds
- example: for Gradle builds, include advice around daemon, options.fork, parallel compile processes, setting compile process maximum heap, test parallel processes, setting test process maximum heap.

3) Documentation about Jenkins slave:
- Existence of/how to tune the jnlp jvm
- How to customise the created pod in a Jenkinsfile
- Need for tuning of job steps (e.g. gradle)

4) Possible blog post?

Comment 1 Jim Minter 2017-11-21 17:22:33 UTC
Also sizing Java to ‘request’ and having limit > request by a small margin possibly best -- reduce penalty of overallocating by small amount and improve resilience

Comment 5 Jim Minter 2018-02-07 17:09:22 UTC
Yes, these will automatically go into the OCP 3.9 docs as well as dedicated when it upgrades to 3.9.

Comment 6 Jim Minter 2021-02-11 17:59:29 UTC
This is super stale.  Closing.


Note You need to log in before you can comment on or make changes to this bug.