I agree with author on the point that queues are best to handle spikes. But when you are talking about scale dealing with millions of messages in short span of time for extended period, queues can never remain empty. Empty queues in this situation would mean that your concurrency is high. When your concurrency is high, this would result in too many concurrent connections to your database which wouldend upcreating bottlenecks for your system.
The system should be designed to handle as many messages as possible ensuring that your resources don't get over burdened. Empty queues where your messages keep getting rejected because your resources are being hammered is not necessarily an efficient system.
> When your concurrency is high, this would result in too many concurrent connections to your database which wouldend upcreating bottlenecks for your system.
If you have a polling queue, as the number of workers grows too large, the overhead of maintaining connections from (worker) -> (stuff in the middle) -> (db or whatever keeps queue state) becomes too high. In the extreme case, you can get into a point of diminishing returns, where adding more workers hurts both throughput and latency in a bad way.
That is - initially you can decrease latency by sacrificing utilization and just adding more workers that usually sit idle. This increases throughput during heavy load, and decreases latency. Until you can't, because the overhead from all the extra workers causes a slowdown up the stack (either the controller that's handling messages, or the db itself that's got the queue state, or whatever is up there). Then when you throw more overhead, you increase latency and decrease throughput, because of the extra time wasted on overhead.
It depends on a lot of different variables.
If you have work items that vary significantly in cost, it can add even more problems (i.e. if your queue items can vary 3+ orders of magnitude in processing cost).
I wrote Namaste, and the N for that looked more like an R. I tried again with Normalization and it produced correct letters. Then I wrote namaste and it wrote it correctly as well. Wonder why it doesn't like "N" in Namaste. :D
I can't express in words the amount of push UPI has provided in India for the digital payments sector. Any shop I have visited in the past year has a QR code on the Front counter. And I am not talking about big shops. I am talking about Hawkers, street vendors, Brick and Mortar shops, roadside Dhabas, Mechanics.
I think the main problem with the accuracy of Wikipedia comes into play when reading about events related to politics or similar controversial topics. I have seen plenty of wrong information on Wikipedia related to recent events which I knew for a fact that were wrong because those events happened in my city and the area in which I reside in.
The information related to the field of science is accurate but can't say the same for modern events or history.
Without even looking, I'm willing to bet that articles related to sex and gender are heavily politicized despite being scientific topics (well, sex at least, gender is questionable). Likely the same for climate change, racial groups, and thousands of other scientific topics.
First of all the title is wrong. Everything mentioned in the article is specific to Php. Secondly, interviews are more algorithm/system design specific rather than being asked what are the new features in latest version of a language.
I completely get that point. I have had that happen to me as well in the past. But since 6 years, whenever I have been to an interview I have never been asked questions so tightly coupled to a language as the article suggests. I have been asked a few questions related to instances where a language doesn't behave as expected. Like `typeof(null)` in js or `1+'1'`. But nothing very very specific. Mostly general questions tend to be more around protocols, design patterns and stuff.
But nothing is for sure. Maybe these questions are still very relevant and it's just that I haven't come across them in interviews recently maybe?
They say that this can be used to safely move injured soldiers out of the battelfield.
I am having hard time understanding that. From the looks of it, this seems like something that dwells in well with the background. Moving subject will definitely be visible as background doesn't stay constant isn't it?
But this is definitely something very innovative and unique.
Quite a good read. I wonder what kind of other details are there in Natyashastra. If anyone can provide a good resource on it I will really appreciate it.
People are going to line up for all of them. Hype sells these days.
reply