3 ms·
This is not just an academic idea for programmers, it is something that you will need to understand to get to the highest levels of engineering. In my career, I
by jerf 9y ago
This is not just an academic idea for programmers, it is something that you will need to understand to get to the highest levels of engineering. In my career, I have cared about how many nanoseconds an operation takes, and I have optimized processes that required several hours to run. That's 9 orders of magnitude down from one second, and if for convenience we go with my hours-long process taking 10000 seconds (2.78 hours), that's four orders of magnitude up.
Obviously, there are people with far more experience than I on the upside; if you work with a process that will run on a 10,000 (CPU) node cluster that will run for 1,000,000 seconds (11.6 days) that's 10 orders of magnitude up from 1CPU for 1sec... and they're actually still quite likely to care about nanosecond level performance, too! Which means that someone working in this situation is spanning 19 orders of magnitude in their day-to-day work.
19 orders of magnitude down from 1 meter is about five orders of magnitude smaller than a hydrogen atom. 19 orders of magnitude up from one meter is about 1000 light-years. It's a pretty big span.
There are not a lot of engineering disciplines, or really, disciplines in general, where spanning this many orders of magnitude in a single job is possible. When it comes time to start optimizing things, you need to know where you stand in the world to make correct decisions: https://stackoverflow.com/questions/4087280/approximate-cost-to-access-various-caches-and-main-memory/4087315#4087315 https://stackoverflow.com/questions/4087280/approximate-cost...
- wiredfool 9y agoTwo that have stuck with me: A nanosecond is about a foot. A pico second is the size of a flake of pepper. Adm. Grace Hopper gave me a nanosecond back in high school, and had a pack of picoseconds at the talk. (But didn't give them away. too small)
- dahart 9y agoThat's extra helpful because these units are approximately the speed of light. Light travels a foot in one nanosecond, and it also traverses the width of a (small, ~.01 inch) pepper flake in a picosecond. When I think about light travelling one foot in a nanosecond, it suddenly puts CPU speeds into proportion for me -- CPUs are now routinely clocking 3-4 cycles per light-foot! A foot is a long way in CPU die lengths, but it's surprising to think about how close CPU's are actually getting to the speed of light already.
- AnimalMuppet 9y agoI remember reading (clear back in the late 1970s, in Datamation magazine) how much fun IBM was having trying to make 2 mainframe CPUs operate coherently with sub-nanosecond clock speeds, when the two CPUs were several feet apart. Just from a speed-of-light perspective, the problem is obvious.
- fabatka 9y agojust a nitpick: The size of atoms is in the 10e-10 m order, the 10e-15 is around the size of nuclei
- mncharity 9y ago> 19 orders of magnitude down from 1 meter is about five orders of magnitude smaller than a hydrogen atom. How to remember sizes is the first section of my slowly-loading wasn't-written-for-public page http://www.clarifyscience.info/part/Atoms http://www.clarifyscience.info/part/Atoms .