So I had nausea for months with no explicit cause. Saw a few doctors, had even a full gastro inspection. My naturalpath then put me on two things and it cleared me up. Both of these are over the counter natural supplements. Might be worth trying...
Pepzin GI (Zinc-L-Carnosine)- 1 capsule 2x per day 75mg
Quercetin- 1 cap 2x per day
If you decide to try this make sure you go with good supplier. E.g. thorne or pure encapsulations
"enqueue() happily overwrites current_tail->next even if it is not null (which may happen if some other producer has enqueued something since we read current_tail)."
Its probably one of the bigger problems of this queue, basically negates the whole structure with this bug.
Sort of. To my knowledge, the original redis was literally signal threaded and performed io on the same threads as managing the DB (asynchronously of coarse). Then after either redis 5 or 6 they added IO threads to redis such that the DB stayed managed by a single thread and network/disk IO happened on the IO threads.
It makes sense for disk persistence to be io but redis is primarily in memory. So I don't think async applies to that aspect of it. In theory that makes it so all operations on the database from the user perspective are serial.
Not sure about this that's why I'm asking here for a definitive concrete answer about this.
fwiw, the company I work for has used keydb (multiple clusters) in production for years, under non-trivial load (e.g. millions of req per second). It did serve as a replacement to actual redis clusters, there were major improvements seen by the switch. I can't remember the actual gains as it was so long ago. I do remember it was an actual drop in replacement, as simple as replacing the redis binary and restarting the service. So if you can afford to, maybe try replacing a redis instance or two and see how it goes.
^ This can definitely be the case in a multi-producer/multi-consumer (MPMC) scenario if CAS is involved with loops. Great care has to be taken when writing MPMC data structures without locks that are more performant then lock equivalents; they are far more complex. I think it should be called out that it seems most (if not all) of the data structures provided are single producer/consumer which generally always have much simpler designs (and limitations of use) then MPMC.
The company I work for is a partial .net shop and runs a number of backend services on .Net core with Linux servers. So at the very least its a very real option in the services space. Can't speak to any UI needs.
I'm not even sure why you would attempt a study like this. It purely observational driven. There is no way to gauge whether the opposite parties policies would have resulted in more/less deaths. For all we know the decision made at the time (even with deaths) was the best possible outcome.
upvote and amplify this -- there are hundreds of massive factors that are not at all causative via political voting. I have heard obesity rates mentioned in other comments, and that is consistent with trends I have seen.
edit: hah- I said "obesity" and "massive factors" .. B&B score
This study is essentially saying the same thing that Jonathan Metzls' book, Dying of Whiteness said in 2020, in that a major cause of this is red controlled states rejecting Medicaid expansion vs. blue states embracing it leads to obvious worse outcomes for those folks who lack healthcare coverage.
He is not exactly wrong... email could be a bit better phrased and mandating X hrs may be a bit extreme. Overall though his main point about a great product not being built over the phone IMO is correct. At the very least you stand a substantially smaller chance of doing so...
I think the part that people most take issue with is the "you have to spend 40 hours in the office (the other 40 hours you are expected to work per week you can do from home)" part...
Pepzin GI (Zinc-L-Carnosine)- 1 capsule 2x per day 75mg Quercetin- 1 cap 2x per day
If you decide to try this make sure you go with good supplier. E.g. thorne or pure encapsulations