Imiphumela yokuhlola ukukhishwa kwakamuva kwe-Redis 8.0 kanye ne-Valkey 8.1 DBMS yethulwa, lapho ukulungiselelwa kokusebenza okubalulekile kwamenyezelwa khona. Kuzo zonke izivivinyo ezenziwe, imfoloko eyakhiwe umphakathi iphumelele iphrojekthi yokuqala, ikakhulukazi ngenxa yokuqaliswa kwe-Valkey yomshini omusha wokucubungula okokufaka okunemicu eminingi/okuphumayo ngemodi engavumelaniyo, edluliselwe kuphrojekthi yi-Amazon.
Endaweni yokuhlola ye-AWS Graviton4 c8g.2xlarge enama-VCPU angu-8, i-Valkey 8.1.1 ifinyelele izicelo eziyizinkulungwane ezingu-999.8 ze-SET ngomzuzwana, kuyilapho i-Redis 8.0 izuze izinga lezicelo eziyizinkulungwane ezingu-729.4 ngomzuzwana. Sekukonke, ukusebenza kwe-Valkey bekungaphezulu ngo-37% kune-Redis yokusebenza kwe-SET kanye no-16% ngaphezulu kwe-GET. Ngesikhathi esifanayo, uma kuqhathaniswa ne-Redis, i-Valkey ibonise ukuncishiswa kwe-SET ngo-30% kanye nokwehliswa ngo-60% kokubambezeleka kwe-GET.
Ukuhlaziywa okuhlukile kwenziwe koshintsho ekuphumeni nasekubambezelekeni kuye ngenani lamaphrosesa ahambisanayo kumodi yokucubungula ye-I/O enezintambo eziningi. Kufika emiculweni emi-3, i-Valkey ne-Redis ibonisa cishe imiphumela elinganayo, kodwa bese kuba u-Valkey ehola. Ngemicu engu-6 ohlelweni olunama-VCPU angu-8, ukusebenza kwe-Valkey kwakuyizicelo ze-SET eziyizinkulungwane ezingu-678 ngomzuzwana, kanti i-Redis yayiyizicelo eziyizinkulungwane ezingu-563 ngesekhondi enomkhawulo wokuxhumana okungu-256 ngesikhathi esisodwa. Lapho inani lokuxhumeka likhuphuka laya ku-400, ukusebenza kwe-Valkey kukhuphuke kwafinyelela kuzicelo eziyizinkulungwane ezingu-832 ze-SET ngomzuzwana.
Ngemva kokuthuthukisa ukuphatha iziphazamiso kusistimu ukuze kwehliswe inani lokushintshwa komongo ku-Valkey, sikwazile ukukhuphula ukusebenza kufinyelele kuzicelo eziyizinkulungwane ezingu-999.8 ze-SET ngomzuzwana. Umongo wokuthuthukisa wehlele ekwabeni ama-VCPU angu-2 okuphatha ukuphazamiseka nokubophezela ama-VCPU angu-6 asele kuchungechunge lokucubungula lwe-Valkey ne-Redis I/O ukuze kuqedwe ukufuduka kwezibambi phakathi kwama-CPU. I-sudo ethtool -L en34 ihlangene 2 # khawula inani labaphathi be-IRQ ku-2 grep en34 /proc/interrupts # bona ukuthi yiziphi izibambi ezihilelekile (99 kanye no-100) echo 1 | I-sudo tee /proc/irq/99/smp_affinity # bopha isibambi 99 kuya ku-core 1 echo 2 | I-sudo tee /proc/irq/100/smp_affinity # bopha isibambi esingu-100 ku-core 2 # Qala i-DBMS (ye-Redis, shintsha i-valkey/valkey:8.1.1 ibe yi-redis:8.0) ngesiqukathi esibophezela kuma-CPU cores 2-7 docker run —network=»host»-rmc \=»2set i-valkey/valkey:7 \ -gcina «» -appendonly cha -io-threads 8.1.1 \ -inombolo yemodi evikelekile -inkumbulo enkulu engu-6gb
Ukuze kuhlolwe ukusebenza, kwasetshenziswa umyalo olandelayo: idocker run —network=»host» —rm —cpuset-cpus=»2-7″ \ valkey/valkey:8.0.1 valkey-benchmark \ -h 172.31.4.92 -p 6379 -t SET,GET -n 100000000 — imicu 256 -d 3000000
Source: opennet.ru
