ashutosh chaudhary

@soumya-codes I have some data: ### 1. Stats Unix Sockets: Cmd: `memtier_benchmark -S /tmp/dice.sock --clients 30 --threads 10 --ratio=1:1 --data-size 256 --requests=100000` Result: ``` 10 Threads 30 Connections per thread...

@soumya-codes Few conclusions from above benches: 1. unix sockets have lesser misses compared to TCP 2. unix sockets outperforms TCP for larger percentiles 3. I have not super-optimised unix sockets...

@soumya-codes For some reason, The TCP tests are only running at 50% capacity, compared to unix socket ones. I missed to note that out earlier, but I noticed a lot...

> @codeasashu I see you are running 10 clients each running 10 threads in case of TCP and 5 clients each running 10 threads. Can you please compare the latency...

@soumya-codes Following is the benchmark from my linux machine: ### 1. Unix sockets CMD: `memtier_benchmark -S /tmp/dice.sock --clients 30 --threads 10 --ratio=1:1 --data-size 256 --requests=100000` Output: ``` 10 Threads 30...

@JyotinderSingh Can you escalate this one?

@JyotinderSingh Sure. But I do not understand how a benchmark winner, an additional connection method, can't align with something that resonates on same featureset (i.e real-time). This doesn't even break...

@soumya-codes Thanks for clarifying this. I am completely aligned with your points. I too am passionate on adding any values which can make dicedb a better realtime db. Looking forward...

Hey @lucifercr07 Can I work on this?