Why is the free dragonfly io utilized so much?

Describe the bug Idle dragonfly with high physical machine IO footprint, but no high IO write and read operations.

Screenshots sudo iotop -b -n 1 |head -n 50

pidstat -dl -p 25966

lsof -p 25966

Environment (please complete the following information):

OS: [Debian GNU/Linux 11]
Kernel: Linux 5.10.0-30-amd64 #1 SMP Debian 5.10.218-1 (2024-06-01) x86_64 GNU/Linux
Containerized: Physical machine direct deployment
Dragonfly Version: [dragonfly-v1.22.2]

Physical Machine Environment CPU 40 core Memory 128GiB Disk 1.8T SAS(Not SSD)

Additional context In response to this issue, where the IO footprint is high, but there are no obvious disk write and read operations, I understand that there are no more than a few reasons that can cause high IO for cached instances:

save alive bgsave operation is being carried out, resulting in the RDB file write disk is more centralized.
replica instance pulling bgsave files generated by the disk to cause a large number of read operations
log printing is more frequent, resulting in greater pressure on the SAS disk IO.
Frequent opening and closing of file handles by the dragonfly process
hard disk failure

According to the phenomenon, dragonfly opened 40 threads, almost full of all the cpu io processes.

It's true that I didn't specify the cpu resources that dragonfly can take up, but it shouldn't produce such a large IO footprint when there are no read/write accesses, I don't know if it's a bug or if I'm just lacking understanding of dragonfly's features.

Attached are the contents of my conf file,I wonder if there's a misconfiguration.

--pidfile=/home/dba/dragonfly/dragonfly7379/dragonfly.pid

--log_dir=/home/dba/dragonfly/dragonfly7379
--logtostderr=false
--logtostdout=false
--max_log_size=500

--dir=/home/dba/dragonfly/dragonfly7379
--max_log_size=20
--version_check=true
--port=7379
--list_compress_depth=0
--cluster_mode=emulated

--maxclients=64000
--maxmemory=10Gib

--bind=10.46.128.11
--admin_bind=17379
--pipeline_squash=10
--tcp_keepalive=1800
--rename_command=
--hz=80
--keys_output_limit=8192

--compression_level=0
--compression_mode=0
--list_compress_depth=0

--admin_nopass=false
--multi_eval_squash_buffer=4096

--df_snapshot_format=true
--dbfilename=dragonfly7379-dump

Looking forward to the answer, thanks!

dragonflydb / dragonfly

Why is the free dragonfly io utilized so much? #3786