joha4270
Joined 2 years ago
Joined 2 years ago
But otherwise chains of microwave links does get much closer to c in applications where you want absolute lowest latency (or much more commonly, when digging a fiber line is too expensive)
Of course, it depends on the altitude of the satellite but speed of light in a fiber optic is only ~2/3rds of speed of light in a vacuum so you can afford some detour
Surely it isn't cheap, but given the price of the hardware, does it add substantially to the total cost of a datacenter?
My grandmother keeps a little notebook with detailed instruction on how to do things such as sending a message on facebook or pay a bill using netbank.
For a lot of things, the choice isn't going to be doing it herself or giving orders to the computer. Its going to be not doing it or giving orders to the computer.
Even if it will look very inefficient to people such as you or me
And if my experience from embedded development is in any way transferable, they're probably fairly spread out and probably takes a fairly big chunk of address space too.
It's not about lights, it's about electricity always being available. And well, always having power available (for domestic, but also for expensive production facilities that looses money while idle) using renewables is a lot more expensive than generating most of your power with renewables
This allows it to split complex instructions into multiple operations instead of having dedicated hardware for it.
High performance cores can also do the opposite trick of "fusing" two instructions into a single uOp: The usual example is compare-and-branch
For the vast majority of non-number-crunching code any theoretical difference between instruction sets vanishes in the noise of core design.
Not to say it isn't a great game, it has managed to steal a great deal of my time. With the caveat that its very unpolished and clearly straining under a load bearing amount of duct tape