@PoornimaNimo He saves on my cable bill.
This idea of liking him is a bit convoluted. When the philosophy of entertainment gets attacked, he comes to rescue. This paradigm is very ingrained in his constitutional identity. We must do caste census on this idea of liking him.
@systemdesignone One key detail that needs to be added is around atomicity between db read and write.
Also, would be good to call out parties as client or server instead of “they”.
BTW, I love your short but informative tweets.
@iavins Netezza database supports writing user-defined functions, table functions and aggregates in many languages. It is still one row at a time. Not familiar with WASM.
@iavins@simonw The word “local” is ambiguous. If the timestamp is generated at the server sitting in a cloud and unless you have laws to govern data within country, you won’t know what value it would be. UTC is the universal truth.
@arpit_bhayani SQLite would have its own overhead too before its own WAL. Since you are on a great path of building high performance Redis, I am sure you will be creating abstraction over whichever method of WAL you will be using so can switch easily. You can choose SQLite for the speed of dev.
@arpit_bhayani Should buy a pencil as well. I bought this for my iPad 8th generation. Still going well for 4 years now. Or buy the Apple one.
https://t.co/qe4ZgJJyh4
@mumbaiheritage Realistically, how much would it cost to get a used Tesla from abroad/US to India legally?
The thing is, moment you get on a road, all autos, bikers get to doing it without any responsibility.
@mgill25 Wouldn’t read from my multiple threads cause constant random seeks which will slow down the read?
How does larger than memory relate to the problem?
@iavins It is a theoretical problem to think, not solve. What is the practical use? What is the guarantee that client would resume back timely? It is a wishful thinking. Is it desirable to have a “long running” transaction like that in a transactional db?
@iavins@DominikTornow because it is the I/O (from multiple fds) that is being multiplexed using select()/poll() to a single thread (the server). I am actually repeating what Dominick said.
You could design a map of fd to thread and hand over request to each thread. That won’t be called multiplexing.
@iamdvr@sivalabs Sorry I meant I prefer curly braces (verbose) instead of indentation to mark code blocks. Would definitely use indentation for readability.