@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!

@arambh-gaur

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

@kommisettyveerendranath53

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

@vikrantkumar4431

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

@kalpeshmali8498

Itni deep me reddis padai hai aapne sir thank you very much sir  ❀️πŸ”₯πŸ™πŸ™πŸ™πŸ™

@sahajarora2162

Beautifully explained. Thank you!

@rktpro

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

@lonelyteapot

An incredibly simple yet detailed explanation, thank you

@sergioliberati9192

this is a really good explanation πŸ‘πŸ‘πŸ‘

@tejpalkhachane1965

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

@jasonngan5747

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

@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

@chetansharma5514

@Asli Engineering :-  I like the content of your playlist. Request you to make a series on Object storage technology ( a detailed one which covers the internal such as how the data is organised and stored on physical hardware ) .. I have been searching internet for this details but have not found anything so any kind of help would be highly appreciated.

@cnkumar20

having worked with asyncio of python lib, made total sense. (python is also single process due to GIL)

@SatSun_xplorer

This channel should gain more reach ❣

@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

@gaengedev2583

thanks bro

@anantsharma13

so Redis use similar I/O handling as NodeJS to make things faster and efficient use of resources.

@akashanand3783

Very well explained. Thanks a ton😊

@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?