Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU 100% iowait #2444

Closed
BlackYuzia opened this issue Jan 19, 2024 · 1 comment
Closed

CPU 100% iowait #2444

BlackYuzia opened this issue Jan 19, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@BlackYuzia
Copy link

Describe the bug

When I run dragonfly docker container I get 100% CPU load (iowait)
image

If I disable container, then I get all normal
image

To Reproduce
Steps to reproduce the behavior:

  1. Run docker container with dragonfly:latest image
  2. Open htop and enable Detailed CPU Time
    image
  3. Profit

Expected behavior
Didn't consume all CPU Time for iowait

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • OS: Ubuntu 22.04
  • Kernel: 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  • Containerized: Docker
  • Dragonfly Version: latest (idk what exactly, image hash sha256:ac30f1740e1aaeb8edd697b823a1ca747ee05282b872fffb769fabfdafb0d40a)

Additional context

I have installed swap with zram.
vm.swappines=60

version: "3.9"

services:
  dragonfly:

    hostname: "dragonfly"
    image: "docker.dragonflydb.io/dragonflydb/dragonfly:latest"
    ulimits:
      memlock: -1
    volumes:
      - "dragonfly-data:/data"
    restart: always
    networks:
      - dragonfly-vnet

volumes:
  dragonfly-data:

networks:
  dragonfly-vnet:
    external: true

Maybe I miss something, feel free to ask if you need something else too.

@BlackYuzia BlackYuzia added the bug Something isn't working label Jan 19, 2024
@romange
Copy link
Collaborator

romange commented Jan 19, 2024

duplicate of #2181 #2270 #2287

@romange romange closed this as not planned Won't fix, can't repro, duplicate, stale Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants