MOSU-395 perf: GC max pause 시간 100ms로 설정

[wlgns12370]

✨ 구현한 기능

• GC max pause 시간 100ms로 설정

📢 논의하고 싶은 내용

• x

🎸 기타

• x

Summary by CodeRabbit

• Chores
  • Optimized JVM performance settings to improve application stability and resource efficiency.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The Dockerfile's ENTRYPOINT instruction is refactored from a single line to a multi-line array format, adding JVM tuning parameters for garbage collection (G1GC with 100ms pause target) and memory configuration (2GB heap). Existing timezone and urandom settings remain unchanged.

Changes

Cohort / File(s)	Summary
JVM Configuration & Formatting Dockerfile	Restructured ENTRYPOINT from single-line to multi-line array, adding JVM heap size (-Xms2g, -Xmx2g) and garbage collection flags (-XX:+UseG1GC, -XX:MaxGCPauseMillis=100) while preserving existing timezone and urandom settings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5–10 minutes

• Verify JVM memory settings (-Xms2g, -Xmx2g) are appropriate for the deployment environment
• Confirm G1GC with 100ms pause target aligns with performance requirements and container resource limits
• Check that existing environment variables and runtime behavior are unaffected by the restructured ENTRYPOINT array format

Poem

🐰 With G1 garbage collecting, memories aligned,
Two gigs of heap, performance refined,
The docker hops faster, pauses less keen,
A tuned JVM—the best I've seen! ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch perf/mosu-395

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4d587cb and 36c6206.

📒 Files selected for processing (1)

• Dockerfile (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @wlgns12370, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

이 PR은 Dockerfile에 가비지 컬렉션(GC) 관련 설정을 추가하여 애플리케이션의 성능을 최적화하는 것을 목표로 합니다. G1GC 사용 및 최대 GC 일시정지 시간 제한을 통해 애플리케이션의 응답성과 안정성을 향상시킬 수 있습니다.

Highlights

• GC 설정 추가: Dockerfile에 G1GC를 사용하고 최대 GC 일시정지 시간을 100ms로 설정하는 옵션이 추가되었습니다. 또한, 힙 메모리 초기 및 최대 크기를 2GB로 명시적으로 설정했습니다.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

이 PR은 GC 최대 정지 시간을 100ms로 설정하고 G1GC를 활성화하며 힙 크기를 2GB로 고정하여 JVM 성능을 튜닝합니다. 전반적으로 좋은 변경이지만, Dockerfile의 ENTRYPOINT 설정에 대해 몇 가지 개선 제안 사항이 있습니다. Java 21에서는 G1GC가 기본값이므로 관련 플래그는 제거할 수 있으며, 하드코딩된 힙 크기를 환경 변수로 대체하여 유연성을 높이는 것을 고려해볼 수 있습니다.

[gemini-code-assist]

Java 11 이상(현재 Amazon Corretto 21 사용)에서는 G1 GC가 기본 가비지 컬렉터이므로 -XX:+UseG1GC 플래그는 중복됩니다. 설정을 더 간결하게 유지하기 위해 이 플래그를 제거하는 것이 좋습니다.

ENTRYPOINT [
  "java",
  "-Duser.timezone=GMT+9",
  "-Djava.security.egd=file:/dev/./urandom",
  "-XX:MaxGCPauseMillis=100",
  "-Xms2g",
  "-Xmx2g",
  "-jar", "/app.war"
]

[gemini-code-assist]

힙 크기(-Xms2g, -Xmx2g)가 하드코딩되어 있습니다. 이렇게 하면 모든 환경에서 동일한 힙 크기를 사용하게 되어 유연성이 떨어질 수 있습니다. 예를 들어, 로컬 개발 환경에서는 더 작은 힙을 사용하고, 프로덕션 환경에서는 더 큰 힙을 사용해야 할 수 있습니다.

Docker 이미지 재빌드 없이 환경에 따라 힙 크기를 조절할 수 있도록 환경 변수를 사용하는 것을 고려해 보세요. 예를 들어, ENTRYPOINT를 쉘 형식으로 변경하고 HEAP_SIZE와 같은 환경 변수를 사용할 수 있습니다:

ENTRYPOINT ["/bin/sh", "-c", "exec java ... -Xms${HEAP_SIZE:-2g} -Xmx${HEAP_SIZE:-2g} ... -jar /app.war"]