Performance Optimization: Difference between revisions
Jump to navigation
Jump to search
(Added Knowledge Graph section) |
(Fix: remove --- horizontal lines (7 removed)) |
||
| Line 18: | Line 18: | ||
* 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | * 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | ||
== Purpose == | == Purpose == | ||
| Line 28: | Line 27: | ||
* Non-goals: 다른 주제로의 확장 | * Non-goals: 다른 주제로의 확장 | ||
== Key Concepts == | == Key Concepts == | ||
| Line 42: | Line 40: | ||
|} | |} | ||
== Detailed Explanation == | == Detailed Explanation == | ||
| Line 67: | Line 64: | ||
|''Recommended Values: Start with doubling the default and adjust based on your server’s traffic load'' | |''Recommended Values: Start with doubling the default and adjust based on your server’s traffic load'' | ||
== Best Practices == | == Best Practices == | ||
| Line 75: | Line 71: | ||
* 테스트 환경에서 먼저 검증 | * 테스트 환경에서 먼저 검증 | ||
== References == | == References == | ||
| Line 81: | Line 76: | ||
* [https://wiki.hpcmate.com Performance Optimization] | * [https://wiki.hpcmate.com Performance Optimization] | ||
== Related Pages == | == Related Pages == | ||
| Line 90: | Line 84: | ||
* [[Network]] | * [[Network]] | ||
[[Category:Server]] | [[Category:Server]] | ||
Latest revision as of 11:30, 17 July 2026
Overview
Performance Optimization에 대한 기술 문서입니다.
Summary
- 무엇인가? - Performance Optimization
- 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
- 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
Purpose
이 문서가 존재하는 이유
- Goal: Performance Optimization에 대한 기술 정보 제공
- Scope: Performance Optimization의 개념, 사용법, 설정
- Non-goals: 다른 주제로의 확장
Key Concepts
| Concept | Description | Related |
|---|---|---|
| Performance Optimization | HPC/서버 환경에서 중요한 기술 개념 | Linux, Server |
Detailed Explanation
Linux is known for its flexibility and ability to be customized, which allows system administrators to adjust its behavior to achieve top performance through fine-tune its kernel parameters.[1] in general, Real-time tuning for benchmark can be done using sysctl -w command and permanent change by editing /etc/sysctl.conf and sysctl -p HPCMATE DLS system provides pre-configured kernel level optimization and UCM (Universial Cluster Manager) provides real-time kernel level optimization via real-time system monitoring. TCP/IP stack parameters in Linux offers powerful possibilities for improved network performance.
| Key parameter | Description | Recommendation |
|---|---|---|
| ipv4.tcp_fin_timeout | This controls how long a connection stays in the “FIN-WAIT-2” state after it’s gracefully closed. Lowering this value (default: 60 seconds) can free up resources faster. particularly useful for servers handling lots of short connections | Recommended Value: 20-30 seconds
|
| ipv4.tcp_tw_reuse | This allows the reuse of sockets in “TIME-WAIT” state. On busy servers, enabling this parameter helps manage high loads more efficiently by enabling quicker recycling of connections | ipv4.tcp_tw_reuse: Recommended Value: 1 (Enable) |
| ipv4.tcp_max_syn_backlog | This value controls the maximum number of connection requests that the server can queue up while waiting for full three-way handshake completion. Increasing this value helps prevent dropping new connections when your server is under heavy load | Recommended Values: Start with doubling the default and adjust based on your server’s traffic load
Best Practices
References
Related PagesKnowledge GraphRelated |