sysctl vm.overcommit_memory=2. However, programs for *nix-based systems usually expect overcommit to be on, for example, to support fork(). This is a stark contrast with Windows NT model, where an allocation will fail if it doesn't fit in the remaining memory+swap.
I have a way simpler explanation. IEEE 754 double can only represent integers up to 2^53 without precision loss, so if you naively average two numbers greater than 2^52, you get an erroneous result.
It just so happens that 2^52 nanoseconds is a little bit over 52 days.
I've seen the same thing with AMD CPUs where they hang after ~1042 days which is 2^53 10-nanosecond intervals.
Yes, you can chuck your SSD into a freezer. Data retention time increases exponentially in lower temperatures, so keeping it in a regular +4C fridge is enough to extend retention by decades.
Just remember to heat up the disk before writing and after storage.
It really doesn't help that it's written in ancient K&R C, but if you spend ten or so minutes just staring at it, familiar shapes and patterns start to appear. (Give it a try!)
Incidentally, it's in line with how APL code looks like an alien artifact at first, but you get used to it fast if you have spatial reasoning to wrap your head around reshaping and transposing.
In datacenters, you're mostly limited by the power (and thus cooling). Most commercial DCs only let you use up to about 10kW per rack. For standard 40U racks it's just 250W/RU, give or take.
There are niche expensive datacenters with higher power density, but as it stands, exotic multi-kW hardware at scale makes sense if you either save a ton on per-node licensing, or you need extreme bandwidth and/or low latency.
>why do we measure time in hours, days, weeks, months, and years rather than in decaseconds, hectoseconds, kiloseconds, megaseconds, etc.?
We don't use them generally because at the time of French Revolution, due to taxes, standardizing the state units of measurement of physical goods was a much more pressing concern than time. (If I were to guess, there were no work hours limits, and thus it just hadn't crossed the popular mind). Weeks were changed to have ten days though.
That's not to say that they hadn't tried: decimal time was mandatory for a few years before they realized that there were too many clocks around, and pushing decimal time can actually turn people hostile against the then-new metric system.
We still kinda sorta use them in form of fractions of Julian days.
I'm pretty sure Lovecraft was at most a passing thought. The more immediate context would be the Putin's internet "AMA" in 2006[1], where "how do you feel about the awakening of Cthulhu" became a meme after becoming the second most popular question. Through the years, it and its associated memes like "fhtagn", "will devour brains", lost their connection with the origin and became a part of the background meme noise. (Compare it with how you don't think about /b/ any time your rickroll someone.)
When operating a complex system like Reddit, you know that something is going to happen during a significant event, but you generally don't know exactly what will break first.
What's worse is that the system evolved as a response to the previous similar event, and what broke now is probably not what had broken in the past.
Individually disposable, yes. But if you have a cluster of those, and you powered them on at the same time -- as it often happens -- you're in for an exciting ride when your servers start rebooting almost simultaneously, give or take a few minutes.
There are always bugs in silicon, just like there are bugs in software. They mostly show up under "a highly specific and detailed set of internal timing conditions". There are 40 documented erratas on EPYC 7002s alone; there are 35 in the 13gen Intel CPUs, including, curiously, RPL038, "Processor Exiting Package C6 or C8 May Hang". Mobile ARM chip manufacturers are notoriously bad at documenting their bugs, so who knows how many they have.
This one is interesting because its preconditions are so trivial, and it will affect many more people than usual.
Precisely. Compare your comment with these excerpts from the article:
>Windows 95 is reasonably fast in performance, and is not compromised by the arguably frivolous animation and eye candy features in Windows 98 and newer versions.
>I prefer to have as much native compatibility as possible with DOS applications such as older games I own.
Windows 95 was released 13 years prior to the article, roughly the same time span as between Windows 7 release and today. Windows 7 is still installed on a single-digit percentage of computers. It is interesting to see that the reasons outlined in the article could be used almost word-for-word by someone justifying their use of Windows 7.
SSE came along much later. At the time it was common-ish to just slowly send HTML tags. I think at some point there was a gorgeous hack where they dynamically rendered and sent GIF frames with the messages of the chatroom.