So it seems like exposure to microbial loads from farm animals help prevent allergies. But humans have not always kept lifestock - what kind of microbial exposure do pre-agrarian peoples receive?
The previous policy uses weighted round robin (WRR), which is described as:
> weight wi is calculated as qi/ui, where qi and ui represent the recent query-per-second (QPS) rate and CPU utilization of replica i.
The pathological case describes a situation where antagonist loads are soaking up CPU on some on the machines, but WRR equally distributes the load because weight formula prioritizes the utilization of the individual tenant, not of the entire machine. Wouldn't including the the machine utilization (probably downweighted) into the WRR formula also solve the issue?
"After the asset sale to Qoo10 closed on April 19th, ContextLogic had approximately $2.7 billion of NOL carryforwards and approximately $161 million in cash, cash equivalents and marketable securities, which consist of government securities. Combined, this represents the net proceeds from the sale. We have no debt.
We have gone from nearly 500 employees worldwide at December 31st to 12 full-time and part-time employees, including some temporary or contract employees. We are no longer liable for any of our old leases, including our former corporate headquarters in San Francisco."
Ive used Memray and it works great locally. But when I deployed my application over long running processes (i.e. in production) because I want to see memory usage over a long period of time, the profiler outputs get really large, like hundreds of gbs. They cause disk outages and also take forever to download and visualize with the flamegraphs. What do people use to understand memory usage of long running workloads in production?
Ive used Memray and it works great locally. But when I deployed my application over long running processes (i.e. in production) because I want to see memory usage over a long period of time, the profiler outputs get really large, like hundreds of gbs. They cause disk outages and also take forever to download and visualize with the flamegraphs. What do people use to understand memory usage of long running workloads in production?
The Permian basin uses technology that is almost all made in America and is now the largest oil producer on Earth. The industrial base in TX is absolutely incredible and rarely discussed.
Boeing, the modern car industry, Macbooks, Pratt and Whitney, Cummins, Caterpillar, the Norfolk Ship Yards,, the modern cardboard/"fiber" packaging industry, our incredibly green Forestry industry, the growing modular housing industry.
Apple Google Amazon Rocketdyne Tesla HP Cisco Systems
Also every 'smart' person who thought they could talk their way out of a police interrogation and is now spending the rest of their life in prison secured by knuckle dragging brutes.
Idiot Australians who smuggle drugs to/from Indonesia come to mind.
>The difference in intelligence between the police and a singular criminal, especially the police as an organism, is vastly in favor of the police.
I don't agree, as that's highly dependent on that singular criminal and the resources police are willing to expend on catching them. The police definitely have an advantage, as I pointed (most recently) here[0]:
Law enforcement aren't superhuman. They're just as dumb (or smart, but the
really smart ones end up in corner offices rather than police stations like
police and more common criminals) as the next guy. Their big advantage,
especially in a circumstance like this, is that they only have to get it
right (i.e., find some evidence) once. The alleged perpetrator of a crime
needs to get it right (in covering their tracks, destroying evidence, etc.)
every single time to make sure they aren't identified and caught.
Yeah but I'm talking about scenarios where all people needed to do to avoid being locked in a little box for life was either A. Not do the obviously stupid thing that everyone is telling them is stupid and that they should absolutely not do. and B. Shut the fuck up.[0]
There are supposedly brilliant people serving life sentences right now and the only reason they're facing that situation is because they couldn't shut the fuck up when they sat down in a little room with an at best slightly above average intelligence police officer.
The officer had a higher working intelligence in that case.
If I prepare for a test and perform better than someone smarter than me, my working knowledge made me superior at that task, even though I was less intelligent at the time I performed it.
The problem with this comparison is that humans, a marginally superior intellect to the collective evolutionary "intellect" of pathogens, regularly eradicate them.
When you're in a "tight loop" (e.g. a matrix multiplication, which is basically 3 nested loops that only load data, do math, write data), Java's virtual threads just won't yield. So if you write your app in the "wrong" way, you lose concurrency.
There's a lot of discussion about this from the Go side. The original issue was this one: runtime: tight loops should be preemptiblehttps://github.com/golang/go/issues/10958
> it's possible to write a tight loop (e.g., a numerical kernel or a spin on an atomic) with no calls or allocation that arbitrarily delays preemption. This can result in arbitrarily long pause times as the GC waits for all goroutines to stop.
> has put significant effort into prototyping cooperative preemption points in loops, which is one way to solve this problem. However, even sophisticated approaches to this led to unacceptable slow-downs in tight loops (where slow-downs are generally least acceptable).
> I propose that the Go implementation switch to non-cooperative preemption using stack and register maps at (essentially) every instruction. This would allow goroutines to be preempted without explicit
preemption checks. This approach will solve the problem of delayed preemption with zero run-time overhead and have side benefits for debugger function calls
I 100% expect Java will have to do through the same evolution. But first they'll probably try to deny reality for a few years. Funny enough, same as has happened with Go and generics.
I doubt it, since they already did that journey long ago and are now adding virtual threads next to ordinary threads that replaced the original green threads. If you put your long running work into the virtual kind of threadpool, a timing sentinel can easily warn you and after noticing that you easily use the normal threadpool instead.
VertX framework had such a sentinel, but migrating code from the async futures to a normal threadpool can be a bit tedious if your design is poor.
It's been a while since I read up on this, but my understanding is that with OS threads, during a context switch it has to pop the entire process stack, which in Java is 1MB by default. This is expensive. Virtual threads "context switches" have much more lightweight stacks because the JVM knows exactly what kind of state needs to be associated with the virtual thread and thats where the difference lies.
There was a scene in The Northman (2022) which is based on Ibn Fadlan. After seeing the movie I read the account [0] which I found very interesting. This describes the scene in the movie:
> The men came with shields and sticks. She was given a cup of intoxicating drink; she sang at taking it and drank. The interpreter told me that she in this fashion bade farewell to all her girl companions. Then she was given another cup; she took it and sang for a long time while the old woman incited her to drink up and go into the pavillion where her master lay. I saw that she was distracted; she wanted to enter the pavillion but put her head between it and the boat. Then the old woman siezed her head and made her enter the pavillion and entered with her. Thereupon the men began to strike with the sticks on the shields so that her cries could not be heard and the other slave girls would not seek to escape death with their masters. Then six men went into the pavillion and each had intercourse with the girl. Then they laid her at the side of her master; two held her feet and two her hands; the old woman known as the Angel of Death re-entered and looped a cord around her neck and gave the crossed ends to the two men for them to pull. Then she approached her with a broad-bladed dagger, which she plunged between her ribs repeatedly, and the men strangled her with the cord until she was dead.
