Skip to content

NimTechnology

Trình bày các công nghệ CLOUD một cách dễ hiểu.

  • Kubernetes & Container
    • Docker
    • Kubernetes
      • Ingress
      • Pod
    • Helm Chart
    • OAuth2 Proxy
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
    • MetalLB
    • Kong Gateway
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Argo Events
    • Spinnaker
    • Jenkins
    • Harbor
    • TeamCity
    • Git
      • Bitbucket
  • Coding
    • DevSecOps
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
      • Azure Cloud
    • Golang
    • Laravel
    • Python
    • Jquery & JavaScript
    • Selenium
  • Log, Monitor & Tracing
    • DataDog
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
    • NextCloud
  • Toggle search form

[Linux] How to Check Disk Performance (IOPS and Latency) in Linux?

Posted on February 8, 2023July 25, 2023 By nim No Comments on [Linux] How to Check Disk Performance (IOPS and Latency) in Linux?

Mình đã hỏi chat GPT và nó chỉ mình như sau:

1. Monitor I/O Performance Using ‘iostat’ Command: The first and most straightforward way to check disk performance in Linux is to use the ‘iostat’ utility to monitor I/O performance. ‘iostat’ can be used to monitor the I/O statistics of both CPUs and storage devices in a Linux system. It displays output in three sections; CPU utilization, device utilization, and a report of devices, including their read and write I/O throughput performance.

2. Monitor Disk Performance with ‘sar’ Command: You can also monitor disk performance in Linux with the ‘sar’ command. It’s part of the sysstat package, which is usually installed on Linux systems by default. It’s very similar to ‘iostat’, but it gives you a more in-depth view of what’s happening on your system. The ‘sar’ output has two main sections; one for I/O stats and one for block device statistics. Using ‘sar’, you can monitor write and read I/O per second, I/O capacity, I/O latency, and more.

3. Check IOPS with ‘fio’ Command: The ‘fio’ command is a tool that can be used to generate I/O performance data for both reads and writes. It running a series of tests on storage devices to measure their throughput, latency, and IOPS performance. The output of ‘fio’ will give you a rough idea of the I/O capability of your system, although it’s not as detailed as the ‘iostat’ and ‘sar’ tools.

4. Measure Latency and Performance with ‘ioping’ Command: The ‘ioping’ command is another useful tool for checking disk performance in Linux. It’s basically a utility for measuring disk latency, and gives you information on the average and maximum latency for your disk. Plus, it can also be used to measure I/O performance by running multiple I/O operations concurrently.

Sau đó thì mình quyết định sử dụng fio

Reference links:
https://cloud.google.com/compute/docs/disks/benchmarking-pd-performance
https://woshub.com/check-disk-performance-iops-latency-linux/

Bài test của mình trên kubernetes

Mình so sánh local disk của node và pvc thì cài nào nhanh hơn
setup local disk of node: gp3 / IOPS: 3000 / Throughput: 125 MB/s / 200GB
PVC: gp3 / IOPS: 16,000 / Throughput: 600 MB/s

đây là file deployment của mình:

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app.kubernetes.io/instance: openvscode-server
    app.kubernetes.io/name: openvscode-server
  name: openvscode-server
  namespace: nimtechnology-engines-staging
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: openvscode-server
      app.kubernetes.io/name: openvscode-server
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      labels:
        app.kubernetes.io/instance: openvscode-server
        app.kubernetes.io/name: openvscode-server
    spec:
      volumes:
        - name: file-service
          persistentVolumeClaim:
            claimName: pvc-file-service-smb-1
      nodeSelector:
        kubernetes.io/os: linux
      containers:
        - image: gitpod/openvscode-server:latest
          livenessProbe:
            failureThreshold: 3
            httpGet:
              path: /
              port: http
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
          name: openvscode-server
          ports:
            - containerPort: 3000
              name: http
              protocol: TCP
          readinessProbe:
            failureThreshold: 3
            httpGet:
              path: /
              port: http
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
          volumeMounts:
            - name: file-service
              mountPath: /app/downloaded

Install Fio

sudo apt update -y
sudo apt install fio

When running the test, an 8 GB file will be created. Then fio will read/write a 4KB block (a standard block size) with the 75/25% by the number of reads and writes operations and measure the performance. The command is as follows:

đây là bài test trên persistent volume.

fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=fiotest --filename=/app/downloaded/testfio --bs=4k --iodepth=64 --size=8G --readwrite=randrw --rwmixread=75
fiotest: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=64
fio-3.28
Starting 1 process
fiotest: Laying out IO file (1 file / 8192MiB)
Jobs: 1 (f=1): [m(1)][100.0%][r=36.7MiB/s,w=12.4MiB/s][r=9385,w=3181 IOPS][eta 00m:00s]
fiotest: (groupid=0, jobs=1): err= 0: pid=1038: Wed Feb  8 09:16:49 2023
  read: IOPS=6253, BW=24.4MiB/s (25.6MB/s)(6141MiB/251421msec)
   bw (  KiB/s): min=18352, max=37664, per=100.00%, avg=25015.65, stdev=3945.22, samples=502
   iops        : min= 4588, max= 9416, avg=6253.91, stdev=986.30, samples=502
  write: IOPS=2088, BW=8353KiB/s (8553kB/s)(2051MiB/251421msec); 0 zone resets
   bw (  KiB/s): min= 6120, max=12704, per=100.00%, avg=8353.98, stdev=1333.53, samples=502
   iops        : min= 1530, max= 3176, avg=2088.49, stdev=333.38, samples=502
  cpu          : usr=2.30%, sys=7.95%, ctx=2092258, majf=0, minf=6
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued rwts: total=1572145,525007,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
   READ: bw=24.4MiB/s (25.6MB/s), 24.4MiB/s-24.4MiB/s (25.6MB/s-25.6MB/s), io=6141MiB (6440MB), run=251421-251421msec
  WRITE: bw=8353KiB/s (8553kB/s), 8353KiB/s-8353KiB/s (8553kB/s-8553kB/s), io=2051MiB (2150MB), run=251421-251421msec

với bài test trên local disk

fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=fiotest --filename=/root/testfio --bs=4k --iodepth=64 --size=8G --readwrite=randrw --rwmixread=75
fiotest: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=64
fio-3.28
Starting 1 process
fiotest: Laying out IO file (1 file / 8192MiB)
Jobs: 1 (f=1): [m(1)][100.0%][r=5388KiB/s,w=1680KiB/s][r=1347,w=420 IOPS][eta 00m:00s]
fiotest: (groupid=0, jobs=1): err= 0: pid=3390: Wed Feb  8 07:55:33 2023
  read: IOPS=1279, BW=5118KiB/s (5241kB/s)(6141MiB/1228649msec)
   bw (  KiB/s): min= 2832, max= 5792, per=99.99%, avg=5118.98, stdev=273.84, samples=2456
   iops        : min=  708, max= 1448, avg=1279.73, stdev=68.46, samples=2456
  write: IOPS=427, BW=1709KiB/s (1750kB/s)(2051MiB/1228649msec); 0 zone resets
   bw (  KiB/s): min=  976, max= 2104, per=99.99%, avg=1709.37, stdev=126.73, samples=2456
   iops        : min=  244, max=  526, avg=427.32, stdev=31.69, samples=2456
  cpu          : usr=0.39%, sys=1.19%, ctx=2097307, majf=0, minf=7
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued rwts: total=1572145,525007,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
   READ: bw=5118KiB/s (5241kB/s), 5118KiB/s-5118KiB/s (5241kB/s-5241kB/s), io=6141MiB (6440MB), run=1228649-1228649msec
  WRITE: bw=1709KiB/s (1750kB/s), 1709KiB/s-1709KiB/s (1750kB/s-1750kB/s), io=2051MiB (2150MB), run=1228649-1228649msec

Bạn có thể tham khảo thêm các command khác.
https://gist.github.com/githubfoam/a678cfc813c7ede6ca9ecb93e34edd8e

Kubernetes & Container

Post navigation

Previous Post: [Karpenter] Using Karpenter instead of Autoscaling Group.
Next Post: [Helmify] CLI that creates Helm charts from Kubernetes yamls.

More Related Articles

[Datree] Admission Controllers Or CLI? Kubernetes Policy Validations with Datree Kubernetes & Container
[Kubernetes] How to delete namespace is Terminating and very stubborn Kubernetes
[Cosign/Kyverno]Signing And Verifying Container Images With Sigstore Cosign And Kyverno Kubernetes
[Kubeshark] Monitoring and Viewing traffics on Kubernetes easily by Kubeshark Kubernetes & Container
[Case dị – istio] Những case khó đỡ khiến chúng ra suy nghĩ là istio có chạy được hay ko? Isito-EnvoyFilter
[Kubernetes] Gateway API – Ingress And Service Mesh Spec Replacement? Kubernetes & Container

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Tham Gia Group DevOps nhé!
Để Nim có nhiều động lực ra nhiều bài viết.
Để nhận được những thông báo mới nhất.

Recent Posts

  • [Azure] The subscription is not registered to use namespace ‘Microsoft.ContainerService’ May 8, 2025
  • [Azure] Insufficient regional vcpu quota left May 8, 2025
  • [WordPress] How to add a Dynamic watermark on WordPress. May 6, 2025
  • [vnet/Azure] VNet provisioning via Terraform. April 28, 2025
  • [tracetcp] How to perform a tracert command using a specific port. April 3, 2025

Archives

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021

Categories

  • BareMetal
    • NextCloud
  • CI/CD
    • Argo Events
    • ArgoCD
    • ArgoWorkflows
    • Git
      • Bitbucket
    • Harbor
    • Jenkins
    • Spinnaker
    • TeamCity
  • Coding
    • DevSecOps
    • Golang
    • Jquery & JavaScript
    • Laravel
    • NextJS 14 & ReactJS & Type Script
    • Python
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • Azure Cloud
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kong Gateway
    • Kubernetes
      • Ingress
      • Pod
    • Longhorn – Storage
    • MetalLB
    • OAuth2 Proxy
    • Vault
    • VictoriaMetrics
  • Log, Monitor & Tracing
    • DataDog
    • ELK
      • Kibana
      • Logstash
    • Fluent
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2025 NimTechnology.