This. Sometimes I want to see what I'm looking at and then (using that dump as a reference) follow up with a corresponding filter (| jq .key, or | tail -n 30). Sure, I could use less, but then I context switch on exit; no support from the scrollback buffer.
I've probably lost 10ms * 1E5 of my life from the extra PID. But, probably would lose more in the context switch.
Of course mileage may vary with different workloads, but are there any good benchmarks/suites to use for comparison in cases like these? They used YCSB but I don't know if those workloads ([1]) are relevant to modern/typical access patterns nor if they're applicable to SQL databases.
You thinking about running some benchmarks in a bcachefs branch (:pray:)?
I want to see this data structure prototyped in PostgreSQL.
Sure, but on principle, looking at the paper, I'd expect it to outperform B-trees since write amplification is reduced, generally. You thinking about cases requiring ordering of writes to a given record (lock contention)?
Weeks? Try years. As a parent of a newborn, I can confidently say that my wife hasn't had a full night's sleep for even one night since the kid was born in early July - she watches the kid at night (we live in a one bedroom apartment with the crib in our room - it affects me, too, but I try to tune it out and focus on sleep, as breadwinner). She also watches the kid all day while I work (9-11 hours). She's drained. I don't see this getting any easier for at least 12 months. It's a long road.
We don't have family to support us and we can't afford childcare. So, that's our situation. Not complaining, just saying - it's not weeks of a little bit less sleep. It's chronically interrupted sleep for months, maybe years (according to Dr. Ferber), with severe affects to hormonal regulation and mood and weight.
I'm not sure what "memory efficient" means. But, Go sprung as a competitor to Java (portability, language stability, corporate language support/development) and C++ (faster compile times). Can't beat C++ in terms of memory management (performance, guys, not safety) much. But, you can fare well against the JVM, I'm guessing.
Yeah, I think you're wrong. It should only take ~10s. tokio::time::sleep records the time it was called before returning the future [1]. So, all 1 million tasks should be stamped with +/- the same time (within a few milliseconds).
I don't understand how this works in the case of testing many applications running on many machines, where many services on many machines need to communicate with each other. We deploy a mix of systemd services and OCI containers (running on podman and Docker) to different machines, the exact mix on each machine depends on the machine's intended purpose.
We currently run CI tests using QEMU VMs. These VMs comprise a few systems representative of those that we deploy to production.
Does adopting Antithesis mean that all non-containerized applications would need to be OCI-ified and every interaction would need to be mocked? There's a sort of combinatorial explosion that I'm concerned about when I'm thinking about testing/adding a new service to a system: All services on which it depends need to be mocked and all services which depend on it require creating a mocked version of it.
Seems like a lot of work. Can someone please help clarify things for me?
Also, how could we test the behavior of non-application code like drivers or the kernel itself?
> Starting the drug use - sure. But do you think the same of people who are already physically addicted continuing use? And does it matter for the problem itself?
Yes, I think if you're neck deep in a fentanyl and tranq addiction you're making a choice to continue using. That's evidenced by those who chose to stop using. And, yes, assigning responsibility correctly is important.
Note that drug treatment programs almost always require patients to accept responsibility for their outcomes. That's not just empty posturing. That's crucial to solving the problem.
> How much can you achieve...
You'll accomplish much more positive change by focusing on individuals suffering from drug use (that includes non-users). If cracking down on distribution did anything to solve addiction then we still be living in Prohibition and drugs wouldn't be more popular, dangerous, and addictive than ever. Cracking down on distribution only increases inequality measures (look at Mexico today and also the results of applying the "zero tolerance" policy to crack cocaine distributors in the 80s - the African American community is still reeling from heavy-handed administration and enforcement) and accelerates the arms race.