Skip to main content

A downloadable nanosecond

I came across a wonderful video of Grace Hopper (if you don't know who she is go read that Wikipedia article first and the come back here) explaining what a nanosecond is using a visual aid. The aid is a length of wire equal to the distance light travels in one nanosecond. That's 299.8mm (or as she puts it 11.8").


That's a handy length because it fits neatly on A4 and US Letter paper. So, here are downloadable nanoseconds that can be used to make the same point as Hopper. I've prepared both A4 and US Letter versions as PDFs.

Seeing the distance light travels in a nanosecond is interesting because it becomes clear that at the very high frequencies that computers operate at the speed of light and length of cabling become significant. This propagation delay is something that designers of very high speed circuits have to take into account. For example, a machine working 1 GHz has a clock that's ticking once every nanosecond.

Here are the two versions.


Comments

Unknown said…
Another way to illustrate it would be to hold up a 30cm (12inch) ruler.
That's close enough to a light-nanosecond. Maybe we just have 30cm in the UK though.....
3:47 PM
Unknown said…
Back in the early days of PC's, the maximum clock speed was about 33 Mhz because of the time it took data to go between the CPU and memory (plus latching). Special layouts allowed some chips to work at slightly higher speeds, but that speed limit wasn't really broken until they started using asynchronous memory and specialized memory controllers to "burst" the signals between them, and then CPU speeds quickly skyrocketed after that. Special considerations also required those early boards to use near-equal lengths for data signals, and slightly longer clock lines so the data signals arrived and stabilized before the data clock arrived.
11:49 PM
Unknown said…
Back in the early days of PC's, the maximum clock speed was about 33 Mhz because of the time it took data to go between the CPU and memory (plus latching). Special layouts allowed some chips to work at slightly higher speeds, but that speed limit wasn't really broken until they started using asynchronous memory and specialized memory controllers to "burst" the signals between them, and then CPU speeds quickly skyrocketed after that. Special considerations also required those early boards to use near-equal lengths for data signals, and slightly longer clock lines so the data signals arrived and stabilized before the data clock arrived.
11:50 PM
Post a Comment

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl
9 comments
Read more

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your
63 comments
Read more

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of
54 comments
Read more