IOPS: Difference between revisions
(Fix: remove --- horizontal lines (7 removed)) |
({{Status}}/{{TOC}} 템플릿 제거) |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
| Line 17: | Line 8: | ||
* 왜 필요한가? - HPC 및 서버 환경에서 필수 개념 | * 왜 필요한가? - HPC 및 서버 환경에서 필수 개념 | ||
* 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | * 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | ||
== Purpose == | == Purpose == | ||
| Line 26: | Line 16: | ||
* Scope: IOPS의 개념, 사용법, 설정 | * Scope: IOPS의 개념, 사용법, 설정 | ||
* Non-goals: 다른 주제로의 확장 | * Non-goals: 다른 주제로의 확장 | ||
== Key Concepts == | == Key Concepts == | ||
| Line 39: | Line 28: | ||
| [[Linux]], [[Server]] | | [[Linux]], [[Server]] | ||
|} | |} | ||
== Detailed Explanation == | == Detailed Explanation == | ||
| Line 61: | Line 49: | ||
1gbit is about 125MB/sec, divide that by 4KB(block size, for example) or whatever your block size is and you get about 32,768. the max number of IOPS over 1gbit network. | 1gbit is about 125MB/sec, divide that by 4KB(block size, for example) or whatever your block size is and you get about 32,768. the max number of IOPS over 1gbit network. | ||
<references /> | <references /> | ||
== Best Practices == | == Best Practices == | ||
| Line 68: | Line 55: | ||
* 공식 문서 참고 | * 공식 문서 참고 | ||
* 테스트 환경에서 먼저 검증 | * 테스트 환경에서 먼저 검증 | ||
== References == | == References == | ||
* [https://wiki.hpcmate.com IOPS] | * [https://wiki.hpcmate.com IOPS] | ||
== Related Pages == | == Related Pages == | ||
| Line 81: | Line 66: | ||
* [[Hardware]] | * [[Hardware]] | ||
* [[Network]] | * [[Network]] | ||
[[Category:Server]] | [[Category:Server]] | ||
Latest revision as of 13:24, 2 October 2026
Overview
IOPS에 대한 기술 문서입니다.
Summary
- 무엇인가? - IOPS
- 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
- 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
Purpose
이 문서가 존재하는 이유
- Goal: IOPS에 대한 기술 정보 제공
- Scope: IOPS의 개념, 사용법, 설정
- Non-goals: 다른 주제로의 확장
Key Concepts
| Concept | Description | Related |
|---|---|---|
| IOPS | HPC/서버 환경에서 중요한 기술 개념 | Linux, Server |
Detailed Explanation
“IOPS” stands for “Input/Output Operations Per Second.” IOPS is an important performance metric for storage devices that shows number of read/write operations that a storage device can perform per second. A high IOPS number means that a storage device is capable of performing a large number of read and write operations in a very short amount of time. This can be beneficial for applications and systems that require fast and efficient access to storage resources. If there is a sudden drop in IOPS, it could indicate a problem with the storage system or with one of the applications running on the system.
Iotop is an interactive real-time I/O usage monitoring tool to check disk read and write bandwidth usage for each running process on Linux.
#install iotop on Ubuntu
$ sudo apt update
$ sudo apt install iotop
#Check Total IO Usage Per Process
$ sudo iotop -ao
#Check Process ID instead of TID in iotop
$ sudo iotop -P
#Filter by Process id or username
$ sudo iotop -P -p <PID> -p <PID>
$ sudo iotop -P -u <USERNAME1> -u <USERNAME2>
IOPS via network is largely a function of block size divided into bandwidth. 1gbit is about 125MB/sec, divide that by 4KB(block size, for example) or whatever your block size is and you get about 32,768. the max number of IOPS over 1gbit network.
Best Practices
- 최신 버전 사용 권장
- 공식 문서 참고
- 테스트 환경에서 먼저 검증
References
Related Pages
Knowledge Graph
Related