System breaks at 58 connections. 57 connections produces good results.

[JonoCameron]

I am testing Unikraft Redis with Memtier Benchmark. When I start the Unikraft Redis server, with the command:

sudo qemu-system-x86_64 -fsdev local,id=myid,path=$(pwd)/fs0,security_model=none -m 32768 -device virtio-9p-pci,fsdev=myid,mount_tag=rootfs,disable-modern=on,disable-legacy=off -netdev bridge,id=en0,br=kraft0 -device virtio-net-pci,netdev=en0 -kernel "build/app-redis_kvm-x86_64" -append "netdev.ipv4_addr=172.44.0.2 netdev.ipv4_gw_addr=172.44.0.1 netdev.ipv4_subnet_mask=255.255.255.0 -- /redis.conf" -cpu host -enable-kvm -nographic

and then test with memtier:
memtier_benchmark -s 172.44.0.2 -p 6379 --requests=100000 --threads=1 --clients=58

Redis will break.
However, if I test with memtier with 1 less connection
memtier_benchmark -s 172.44.0.2 -p 6379 --requests=100000 --threads=1 --clients=57
I get reasonable results.

redis-cli -h 172.44.0.2 -p 6379
172.44.0.2:6379> config get maxclients
1) "maxclients"
2) "10000"
Suggests that I should have more than enough space. I want to benchmark unikraft redis with 300 clients, how can I fix this problem?

[JonoCameron]

Supporting files

debug_app-redis_kvm-x86_64.md
redis_conf.md