@kommisettyveerendranath53

Thank you Arpit, very nice way of explaining the whole concept behind the redis single threaded model.

@arambh-gaur

What an outstandingly excellent explaination !!! Yes handling mutexes and semaphores has it's own throughput headaches

@lonelyteapot

An incredibly simple yet detailed explanation, thank you

@sahajarora2162

Beautifully explained. Thank you!

@sergioliberati9192

this is a really good explanation 👍👍👍

@jasonngan5747

Very great and thorough content! Thanks for the nice work!

@sharmassahil1991

BTW, the system calls for such network I/O multiplexing are generally either select or epoll. Nice to see an explanation of those someday from you. Good stuff!

@kalpeshmali8498

Itni deep me reddis padai hai aapne sir thank you very much sir  ❤️🔥🙏🙏🙏🙏

@SatSun_xplorer

This channel should gain more reach ❣

@vikrantkumar4431

I used sorted redis sets in my company project for leaderBoard 😅, completely removing db here. Fetched the leaderboard combining two scores into one

@rktpro

Every embedded systems guy who works with C would find the 'single thread' design just another day in life.

@liveforothers1846

@arpit as you said redis create connection fromTCP and in a single thread all those connection comes and execute.  But i have also seen i can only create one connection in redis and that one connection can also serve as many request as multiple connection does. Which is more scaleble single connection with multiple request or connection per request is the ideal practice

@akashanand3783

Very well explained. Thanks a ton😊

@jivanmainali1742

Network IO is slow but execution is fast (in memory ) implies it has no waiting data (queue of commands ) to process thus IO multiplexing seems to be a wonderful solution

@大盗江南

amazing content!!!  Thank you!!!

@jatinmalav7975

NodeJs also works in similar fashion of single thread, if this is the key reason of its fast computation why no other cache tech implemented it at first end?

@jivanmainali1742

Hi Arpit , Is there a way we can limit number of tcp connection to redis at application layer in synchronous way ?

@tejpalkhachane1965

Pls add some videos on api performance improvements, error handling in micro services, performance testing of micro services

@gaengedev2583

thanks bro

@ratnadeepbhattacharya3237

Hi Arpit,  in this video are we using connection and request terms interchangeably in some cases? Also to achieve concurrency in single process mode (Generically speaking in terms of web services and processes like redis) either we can have thread per connection doing read() on socket (waste of thread since we usually have thread pools now especially in web servers) or Async IO + event loop or once connection is created monitor socket when request comes and we get notified trigger read() on it using a thread from thread pool (hybrid of above two) right? Btw great video loved it.