A single cycle of a 4 GHz CPU is 0.25 nanoseconds. This translates to about 7.5 cm of distance. Given that a chip is about 1x1 cm, it takes at least about 1/7 of a clock cycle for a signal to propagate throughout the chip. This is one of the reasons why we can't increase clocks much further without more miniaturization.
When Grace Hopper was doing her nanosecond/microsecond/millisecond explanation back in the day, she often saved the best for last. After handing out nanoseconds to the audience, she then pulled a microsecond out of a bag behind the podium, which was quite the bundle of wire. This I saw back in the mid-70s at a lecture she was giving to the local ACM chapter. She was a hoot. If interested, check out her career. Wikipedia is not a bad place to start.
In the late '80s or early '90s, Admiral Grace Hoppe came to our Data Processing Managers's Association (DPMA) meeting in Little Rock, AR. I still have my nano-second. Having read about her years before her visit, I would always think of her when I hear the term "bug" or "debugging" as she coined the term when her program failed because a moth got on one of the wired circuit boards and cause a short circuit or bridge which caused the program to fail. Hence, bug and debug. (BTW, my first experience with programming was wiring circuit boards for an IBM 402 listing machine in my first job after graduating from college.)
I had gone over 40 years without every truly understanding this, bit of a mind blow really. Can you guess what I will be teaching my daughter about today? Thanks Gary.
This sort of stuff gets very important for programming - android really want you to be conscious of how many clock cycles you are using (and wasting) when doing your programming... looking forward to the future videos.
For games, the important thing is that at 60fps you have just 16.6 milliseconds to process each frame. But that is a long time compared to a nanosecond! 😬
I got to see Grace Hopper when she spoke to our computer club meeting held at Muskingum College in New Concord, OH. It was in the late 1970s. She passed out "nano seconds" to those who attended.
I never knew Grace Hopper had used this analogy. A few years ago, I was explaining to someone how fast CPUs operated using a very similar method. I started with the 300,000 km/s down to nanometers and then pointed out that in the time it took light to travel from the computer screen in front of them to their eyes, the processor has executed around 3 instructions. Of course, the timing requirements on some of the signal lines of processors have been defined in the picosecond range for many years now.
I caught a glimpse of this topic very recently and it's pretty mind blowing how physical limitations shape the design of electronics, looking forward to your next videos !
Nice. But... when you talk about speed of light in vacuum (vectorial) rather than rapidity (scalar and more appropriate), is worth to mention that c constant is actually a "convention", as long as isotropic "c" in "one way direction" is impossible to measure and can even be anisotropic. So they accepted such assumption and moved on.
A CPU with a 3GHz clock has a clock cycle of 1/3 nanosecond. In that time light travels only 10 cm in a vacuum. An electrical signal cannot traverse the motherboard in that time!
That's why SoC - like Apple M1 chip - is the future of fast computing. Combined with RISC architecture, this will eventually replace x86_64 and any other kind of CISC-like cpus architecture. Apples M2 cpu will be on 3nm that will probably houses up to 256GB, 64-core and 64+ GPU cores all on the single die. Imagine the power of computation that we will have for less than 10 Watts. This is the future and it is right now.
Now divide this wire by 4. This is the distance of light between 2 cycles of 4GHz processor. That's why processors aren't cheap. Just imagine - there is billions of transistors and it's impossible to imagine path of electrons across processor while sober. Chears :)
I remember that episode of Letterman. IIRC she went on to show how she explained the delay in satellite communication by holding up one of those wires and saying that there are a whole lot of nanoseconds to the satellite and back.
In one nanosecond, light travels about 300mm (about 12 inches for those in the USA). In one millisecond, sound travels about 300mm ( that's not exact, but close enough). So light is around 1 million times faster than sound.
oh yeah ! I always wondered how atomic clocks were synchronized because if you imagine a signal traveling from one device to another ; by the time it reaches the intended device enough time would pass as to make it a little behind .
That reminds me of the Richard Feynman video with him talking about light and waves. It's so obvious, but it blew my mind when I just stopped and thought about all the types of electromagnetic 'stuff' just whizzing around us at all times and how it all interacts without us even noticing. Always worth a watch.
I was thinking about this yesterday. there are 1 billion nanoseconds in a second. So, CPU does 1 billion operations in a second, if each instruction takes a microsecond, then its about million instructions per second!
First you have Deci and Centi before milli then: Millisecond= 0.001 second or 1x10^-3 Microsecond= 0.000001 second or 1x10^-6 Nanosecond = 0.000000001 second or 1x10^-9 Then Pico.... And so on and so forth.
Just think: computers used to deal in microseconds (8080 and similar processors), but now deal in nanoseconds. And the integrated circuits used to deal in micrometers, but now deal in nanometers. And as chips cross over into picometers, we start to see the importance of picoseconds. Its like somebody planned it all out :-)
Client : Do you know any unit of time less than a second? Me : Yes, millisecond, microsecond etc.... Client : Nice, so you do know... Why don't you give your delivery time in those units for a change??
What I always found a wee bit confusing is a thousandth is called a milli and a millionth is called a micro. Guess historically it derived from a millimetre being a millionth of a kilometre so perhaps originally it should have been called a millikilometre. I think also it is universally accepted that a trillion is a thousand times a billion rather than a billion times a billion.
I went searching and there are even smaller units being the most recent (2020) the "Planck Time" en.wikipedia.org/wiki/Orders_of_magnitude_(time)#Less_than_one_second
Hi Gary. Why don't you have a television? You are such a good presenter. I watch your videos even when I'm not all that interested in the topic because you make it interesting. Bit like I used to watch Jonny Ball as a kid because he could make any subject interesting as do you.
@@GaryExplains HAHAHA. Yes. I missed a word out, "job". Why don't you have a job in television as a presenter? I suppose I missed out two words in fact. Messed that one up, didn't I? :-)
Time is the construct we have invented in order to give a structure to our descriptions of events with regard to cause and effect and chronology. I do not believe it is a dimension we are "moving through". Attempts to view the universe that way merely complicates things, (requiring things like infinite universes existing or branching simultaneously in parallel in order to represent all probabilities) We can say that events in the past did happen, to be sure, but I think we are misled in the direction it implies. There is no past. It does not actually exist. What I mean by this is that there is no place or time in which the Second World War is still happening, being on a different place on the dimension we are travelling through. The breakfast you ate yesterday is not still being eaten, somewhere along this dimension, anchored to a moment with a date we can name. No. What happened may have happened, and the atoms of your breakfast and the atoms of the casualties from WWII are still here, circulating, acting, being atoms. They are still here, and they are now. There are choices I could have made but did not; nothing requires that they be played out in an alternate "lane" of time or a parallel universe amongst infinite optional possibilities - there is no reason to believe that all possibilities must be enacted, and so I feel the "multiverse" idea of infinitely branching possible universes does not hold up to Occam's Razor. I also feel the "dimensionality" of time does not hold up to Occam's Razor. I believe "now" is the only moment that actually exists, that time is not a dimension but a point, a moment, an instant, called the present. This is all that exists. The future does not exist. The past does not exist. There is nothing but the "now". Anyone living in the past would have considered themselves living in the "now", as will anyone living in the future. And they would have been right. The fact that they were once here but exist no longer does not seem to threaten my understanding or require that a "past" exist, no more than rearranging sand into a sandcastle requires that we invoke an imagined world where the sand remains flat forever. I am well aware of the relativistic phenomenon of time-dilation, which expresses that one's perception of the order of events and the speed at which they occur is relative to one's relative speed as they travel through space, but nothing about that suggests that time should require a dimension in order to facilitate this. It might be easier for some minds to grasp relativity by imagining time as a line, allowing for a coiled-spring analogy but I do not see it suggesting that the events described by relativity do not happen without time being a thing that is "travelled through" Basically, now is all there is. Eternity? This is what eternity feels like. You are in it. Now is the eternity we speak of, and the only time that exists. It will be here, forever, always being "now".
And with still reasonably inexpensive solutions like GPS reference with OCXO and/or rubidium timebase ns is too slow. So picoseconds (ps) and femtoseconds (fs) are more appropriate.
@@GaryExplains Yeah, maybe not meaningful in any typical, practical use cases. But as a spec values the 10^-11 range (accuracy at shipment) all the way to 10^-13 (for 24h stability) are seen. Though I'm mainly only familiar with SRS (Standford Recearch Systems) products - their site is "thinkSRS". My clients use these and some other OCXO / rubidium standards for audio systems (I'm not a reseller though - just a tech/design person). So for them their capabilities aren't pushed to their limits. But the difference is surprisingly large compared to running basic quality XO. Of course in complex audio systems using pretty much any master clock gives even larger benefits - but the benefits for going with OCXO + rubidium is more than I thought it could be (I mean for audio - but these are mostly +$100k systems).
@@youkofoxy They are used in many type of systems. Some are simple +$500k 2-channel (stereo) high end systems with products like MSB Technology The Select DAC and Acapella Audio Arts speakers with plasma tweeters etc. And some are large studios with multiple recording, editing and mastering systems. In my own home system I just use a nice reclocker (RME Fireface UFX, but only in digital domain because it's analog side isn't that good - well, other than decent mic stage) with a stable OCXO and AMR DP-777 DAC. So I don't feel the need to have rubidium oscillator or GPS reference (for audio homeuse).
@@youkofoxy For some reason the problem for many (even very expensive and professional) audio products seems to be heavily frequency dependent jitter. Even though their DACs could be advertised and measured to have only few hundred ps jitter this doesn't matter at all to what people hear. That's only a single pulse measurement. The jitter I'm talking about is more "long term" and much, much worse and varies with frequency. That's what sounds so bad to human ears (we don't hear some picosecond differences). It's not exactly the same - but sounds similar than what you get with long, low quality TOSLINK cable (with a lot of internal reflections in "wide" channel). To mostly get rid of that even quite cheap reclocking devices help a lot.
@@GaryExplains I'm just being silly, I think Grace is great and just wanted more things about her shared. She is like a technology hero, like Vint Cerf is a great advocate/communicator. Or Kelsey Hightower. But Linus Torvalds and Richard Stallman, euh... aren't for everyone, as an introduction. Interesting enough the other Linus (Tech Tips) might now be the introduction for many. That's kind of odd to think about. I would say your content is better. Well, different market I guess. Actually, find it fascinating iJustine is still in the game doing relatively the same thing she was doing, what 10 years ago ? And I wonder if her audience changed.
And life (or physics) doesn't stop at nanoseconds. Just think about today CPU's clock speed: 1, 2, 3.. 5 GHz, which means they are working in the sub nanoseconds time range.
I think that millionth and billionth in themselves are hard for people to conceive. Those words alone don't help me understand the duration of a nano second.
@@GaryExplains Thanks for your reply, Gary. If you want to see an amazing demonstration of big numbers check out your fellow RUclipsr's vid: 'The Impossible Hugeness of Deep Time' on the 'It's OK to be Smart' channel. I've watched it and rewatched it many times. I never tire of it. Have a few teacher friends I've referred to it.
A single cycle of a 4 GHz CPU is 0.25 nanoseconds. This translates to about 7.5 cm of distance. Given that a chip is about 1x1 cm, it takes at least about 1/7 of a clock cycle for a signal to propagate throughout the chip. This is one of the reasons why we can't increase clocks much further without more miniaturization.
Wow, that's mind boggling
How does one determine the length of the longest path within a CPU's circuitry?
When Grace Hopper was doing her nanosecond/microsecond/millisecond explanation back in the day, she often saved the best for last. After handing out nanoseconds to the audience, she then pulled a microsecond out of a bag behind the podium, which was quite the bundle of wire. This I saw back in the mid-70s at a lecture she was giving to the local ACM chapter. She was a hoot. If interested, check out her career. Wikipedia is not a bad place to start.
She also had pico seconds :-)
The number of nanoseconds in a second is roughly the same as the number of seconds in thirty years.
In another's words, 3 seconds in computing time is like a life time.
When my wife turned a billion, I had a party for her. Ny my kid is approaching it.
@@hamslabs My eldest grandson has past it. 🙄
946,708,560 nanoseconds??
@@youkofoxy "In other words"
In the late '80s or early '90s, Admiral Grace Hoppe came to our Data Processing Managers's Association (DPMA) meeting in Little Rock, AR. I still have my nano-second. Having read about her years before her visit, I would always think of her when I hear the term "bug" or "debugging" as she coined the term when her program failed because a moth got on one of the wired circuit boards and cause a short circuit or bridge which caused the program to fail. Hence, bug and debug. (BTW, my first experience with programming was wiring circuit boards for an IBM 402 listing machine in my first job after graduating from college.)
I had gone over 40 years without every truly understanding this, bit of a mind blow really. Can you guess what I will be teaching my daughter about today? Thanks Gary.
Shes going to make you so proud at school! God bless her with all the happiness and success in the world! You’re a great dad mate cheers 🍻
You just saved her 40 years 🙏
@@juangal7569 lol
Your way of explanation is superb!!
Glad you think so!
This sort of stuff gets very important for programming - android really want you to be conscious of how many clock cycles you are using (and wasting) when doing your programming... looking forward to the future videos.
For games, the important thing is that at 60fps you have just 16.6 milliseconds to process each frame. But that is a long time compared to a nanosecond! 😬
I got to see Grace Hopper when she spoke to our computer club meeting held at Muskingum College in New Concord, OH. It was in the late 1970s. She passed out "nano seconds" to those who attended.
They have some of those nanosecond wires on display at the American History Museum
Thanks Gary! The visual really puts it all into perspective.
Thumbs up for the Rear Admiral Grace Hopper clip. Truly an amazing lady in the field of computer science, and just overall cool in general. :)
One of the few channels where I like the videos before they’ve even started.
I never knew Grace Hopper had used this analogy. A few years ago, I was explaining to someone how fast CPUs operated using a very similar method. I started with the 300,000 km/s down to nanometers and then pointed out that in the time it took light to travel from the computer screen in front of them to their eyes, the processor has executed around 3 instructions. Of course, the timing requirements on some of the signal lines of processors have been defined in the picosecond range for many years now.
excellent description and comparison
*GARY!!!*
*Good morning Professor!*
*Good morning fellow classmates!*
Stay safe out there everyone!
MARK!
Please make videos about how a web page works in detail like what happens in the browser, network and back end, I love your way of explaining, please
If you wish to make your own nano second measure off 9 inches (for those using imperial units).
I caught a glimpse of this topic very recently and it's pretty mind blowing how physical limitations shape the design of electronics, looking forward to your next videos !
Nice. But... when you talk about speed of light in vacuum (vectorial) rather than rapidity (scalar and more appropriate), is worth to mention that c constant is actually a "convention", as long as isotropic "c" in "one way direction" is impossible to measure and can even be anisotropic. So they accepted such assumption and moved on.
Great video! Thank you for creating it :) The visual representation of nanosecond is amazing!
Gary explains SI-Prefixes
I hope the video is more than just that. I tried (maybe failed) to give some context to those numbers.
@@GaryExplains you did in a really vivid way!
İ feel like Gary needs an astrophysics channel. İ love such videos
Grace Hopper invented software development. Her work on something called Flow-Matic lead to the COBOL programming language.
Relevant dialog begins at the 39,000,000,000 nanosecond time mark.
😂
You were very imprecise. I believe he started the non-intro dialog at approximately 39,034,047,329,529,511 femtoseconds.
Wish I had this clear info about time in my High School Physics Classes.
I hope you explain jitter and such. I've never understood what that measurement is exactly.
A CPU with a 3GHz clock has a clock cycle of 1/3 nanosecond. In that time light travels only 10 cm in a vacuum. An electrical signal cannot traverse the motherboard in that time!
That's why SoC - like Apple M1 chip - is the future of fast computing. Combined with RISC architecture, this will eventually replace x86_64 and any other kind of CISC-like cpus architecture. Apples M2 cpu will be on 3nm that will probably houses up to 256GB, 64-core and 64+ GPU cores all on the single die. Imagine the power of computation that we will have for less than 10 Watts. This is the future and it is right now.
That is something I didn't know I needed
Man, I'm looking forward eagerly. I love to know about time speed and all that stuff.
me with a bachelor degree of physics just couldnt resist clicking the video ,, great job gary
Now divide this wire by 4. This is the distance of light between 2 cycles of 4GHz processor. That's why processors aren't cheap. Just imagine - there is billions of transistors and it's impossible to imagine path of electrons across processor while sober. Chears :)
The Background change is awesome
I remember that episode of Letterman. IIRC she went on to show how she explained the delay in satellite communication by holding up one of those wires and saying that there are a whole lot of nanoseconds to the satellite and back.
In one nanosecond, light travels about 300mm (about 12 inches for those in the USA).
In one millisecond, sound travels about 300mm ( that's not exact, but close enough).
So light is around 1 million times faster than sound.
Yep : Light 300000 km/s (or 300000000 m/s) vs Sound 340 m/s. That's about a million times faster.
Wonderful video!
Eagerly waiting for your next video.
dont know you gary just barely found you, but thank you for the info!!!!
The period at the end of this sentence is roughly how far light can travel in a picosecond.
oh yeah ! I always wondered how atomic clocks were synchronized because if you imagine a signal traveling from one device to another ; by the time it reaches the intended device enough time would pass as to make it a little behind .
Exactly. That will likely be the topic of my next video!
Make a video on time dilation
Thank you for this sir, ❤
The 1st time I tought about this I realized there are always multiple bits in transit on a Gigabit network cable.
That reminds me of the Richard Feynman video with him talking about light and waves. It's so obvious, but it blew my mind when I just stopped and thought about all the types of electromagnetic 'stuff' just whizzing around us at all times and how it all interacts without us even noticing. Always worth a watch.
Good explanation
Glad you liked it!
Oh Gary, my brain hurts.
Sir make more these types of Science videos 👍
Interesting 🤔 thank you
That nanosecond is a lot sorter near the event horizon of a black hole.
super interesting I did the timer test and when i said 60 and looked down it was at about 59.
I have a question how can I calculate a very short pulse between 1nanoseconds this is to calculate the speed of light and thanks
Hmmm so thats how lidar scanners work. Assuming one oscillation is clocked even lower than a nano second. Crazy
I was thinking about this yesterday. there are 1 billion nanoseconds in a second. So, CPU does 1 billion operations in a second, if each instruction takes a microsecond, then its about million instructions per second!
I would of given an example of gaming with latecy.. for example, Eastcoast Australia to Westcoast USA is around 150ms...
First you have Deci and Centi before milli then:
Millisecond= 0.001 second or 1x10^-3
Microsecond= 0.000001 second or 1x10^-6
Nanosecond = 0.000000001 second or 1x10^-9
Then Pico....
And so on and so forth.
Just think: computers used to deal in microseconds (8080 and similar processors), but now deal in nanoseconds. And the integrated circuits used to deal in micrometers, but now deal in nanometers. And as chips cross over into picometers, we start to see the importance of picoseconds. Its like somebody planned it all out :-)
Can mention the length of the nano second. I mean the wire you hold to explain nano second
Thanks 🙏
Why you are my physics professor?
This why.
I didn't hear him mention the wire's length, which is just under 11.8 inches.
Second, Millisecond, Microsecond, Nanosecond, Picosecond, Femtosecond, Attosecond, Zeptosecond, Yoctosecond, Then Planck Second
Thx
What about Zepto Second
Second
Millisecond
Microsecond
Nanosecond
Picosecond
Femtosecond
Attosecond
Zeptosecond
Yactosecond
And finally 'planck time'
Millennium
Century
Decade
Year
Month
Day
Hour
Minute
Second
Exactly 1.3 seconds lights takes to reach from moon to Earth
I had the pleasure of meeting this amazing women many years ago at a computer meeting in MA. Of course she had her wire with her.
nanosecond = ?cm (looks like about a foot (11.7")?
Light speed is crazy thinking about it 🤯
Thanks
Client : Do you know any unit of time less than a second?
Me : Yes, millisecond, microsecond etc....
Client : Nice, so you do know... Why don't you give your delivery time in those units for a change??
What I always found a wee bit confusing is a thousandth is called a milli and a millionth is called a micro. Guess historically it derived from a millimetre being a millionth of a kilometre so perhaps originally it should have been called a millikilometre. I think also it is universally accepted that a trillion is a thousand times a billion rather than a billion times a billion.
1 tick is 100 nano seconds. Such a small expression of time.
How long is a Jillisecond?
Thanks sir Gary (why was picosecond left out? :-)
Stay safe.
God bless.
Because for the videos I have planned, it isn't needed.
I went searching and there are even smaller units being the most recent (2020) the "Planck Time"
en.wikipedia.org/wiki/Orders_of_magnitude_(time)#Less_than_one_second
Gary made a mistake, he said, 1 millionsecobd is the 1millionth of a microsecond. Which is wrong.
Did I? I think i said one thousandths.
The next episode: how many bits are in a byte ))
Grace Hopper did that decades ago.
Eh?
Hi Gary. Why don't you have a television? You are such a good presenter. I watch your videos even when I'm not all that interested in the topic because you make it interesting. Bit like I used to watch Jonny Ball as a kid because he could make any subject interesting as do you.
Why don't i have a television? Or why aren't I on television?
@@GaryExplains HAHAHA. Yes. I missed a word out, "job". Why don't you have a job in television as a presenter? I suppose I missed out two words in fact. Messed that one up, didn't I? :-)
Time is the construct we have invented in order to give a structure to our descriptions of events with regard to cause and effect and chronology.
I do not believe it is a dimension we are "moving through". Attempts to view the universe that way merely complicates things, (requiring things like infinite universes existing or branching simultaneously in parallel in order to represent all probabilities)
We can say that events in the past did happen, to be sure, but I think we are misled in the direction it implies.
There is no past. It does not actually exist. What I mean by this is that there is no place or time in which the Second World War is still happening, being on a different place on the dimension we are travelling through. The breakfast you ate yesterday is not still being eaten, somewhere along this dimension, anchored to a moment with a date we can name. No. What happened may have happened, and the atoms of your breakfast and the atoms of the casualties from WWII are still here, circulating, acting, being atoms. They are still here, and they are now.
There are choices I could have made but did not; nothing requires that they be played out in an alternate "lane" of time or a parallel universe amongst infinite optional possibilities - there is no reason to believe that all possibilities must be enacted, and so I feel the "multiverse" idea of infinitely branching possible universes does not hold up to Occam's Razor.
I also feel the "dimensionality" of time does not hold up to Occam's Razor.
I believe "now" is the only moment that actually exists, that time is not a dimension but a point, a moment, an instant, called the present. This is all that exists. The future does not exist. The past does not exist. There is nothing but the "now". Anyone living in the past would have considered themselves living in the "now", as will anyone living in the future. And they would have been right. The fact that they were once here but exist no longer does not seem to threaten my understanding or require that a "past" exist, no more than rearranging sand into a sandcastle requires that we invoke an imagined world where the sand remains flat forever.
I am well aware of the relativistic phenomenon of time-dilation, which expresses that one's perception of the order of events and the speed at which they occur is relative to one's relative speed as they travel through space, but nothing about that suggests that time should require a dimension in order to facilitate this. It might be easier for some minds to grasp relativity by imagining time as a line, allowing for a coiled-spring analogy but I do not see it suggesting that the events described by relativity do not happen without time being a thing that is "travelled through"
Basically, now is all there is. Eternity? This is what eternity feels like. You are in it. Now is the eternity we speak of, and the only time that exists. It will be here, forever, always being "now".
Wow boss thank you
what about a picosecond?
And with still reasonably inexpensive solutions like GPS reference with OCXO and/or rubidium timebase ns is too slow. So picoseconds (ps) and femtoseconds (fs) are more appropriate.
Not so sure about that. That will be the subject of an upcoming video in this series.
@@GaryExplains Yeah, maybe not meaningful in any typical, practical use cases. But as a spec values the 10^-11 range (accuracy at shipment) all the way to 10^-13 (for 24h stability) are seen. Though I'm mainly only familiar with SRS (Standford Recearch Systems) products - their site is "thinkSRS".
My clients use these and some other OCXO / rubidium standards for audio systems (I'm not a reseller though - just a tech/design person). So for them their capabilities aren't pushed to their limits. But the difference is surprisingly large compared to running basic quality XO.
Of course in complex audio systems using pretty much any master clock gives even larger benefits - but the benefits for going with OCXO + rubidium is more than I thought it could be (I mean for audio - but these are mostly +$100k systems).
@@tkermi how many channels is this audio system?!
Unless is ultrasonic A/D, microseconds should be more that enough for double digits application.
@@youkofoxy They are used in many type of systems. Some are simple +$500k 2-channel (stereo) high end systems with products like MSB Technology The Select DAC and Acapella Audio Arts speakers with plasma tweeters etc. And some are large studios with multiple recording, editing and mastering systems.
In my own home system I just use a nice reclocker (RME Fireface UFX, but only in digital domain because it's analog side isn't that good - well, other than decent mic stage) with a stable OCXO and AMR DP-777 DAC. So I don't feel the need to have rubidium oscillator or GPS reference (for audio homeuse).
@@youkofoxy For some reason the problem for many (even very expensive and professional) audio products seems to be heavily frequency dependent jitter. Even though their DACs could be advertised and measured to have only few hundred ps jitter this doesn't matter at all to what people hear. That's only a single pulse measurement.
The jitter I'm talking about is more "long term" and much, much worse and varies with frequency. That's what sounds so bad to human ears (we don't hear some picosecond differences).
It's not exactly the same - but sounds similar than what you get with long, low quality TOSLINK cable (with a lot of internal reflections in "wide" channel). To mostly get rid of that even quite cheap reclocking devices help a lot.
And picosecond is a thousandth of a nanosecond.
Is there anything shorted for time ?
@@rishirajsaikia1323 femtoseconds and attoseconds. 1/1000 of pico and 1/1000 of femto respectively.
What about picoseconds and femtoseconds?
I'm disappointed you didn't include pico seconds (as Grace Hopper showed them), because my guess is you might have had some or could get them easily.
I don't need pico seconds for the videos I am making about time.
@@GaryExplains I'm just being silly, I think Grace is great and just wanted more things about her shared. She is like a technology hero, like Vint Cerf is a great advocate/communicator. Or Kelsey Hightower. But Linus Torvalds and Richard Stallman, euh... aren't for everyone, as an introduction. Interesting enough the other Linus (Tech Tips) might now be the introduction for many. That's kind of odd to think about. I would say your content is better. Well, different market I guess. Actually, find it fascinating iJustine is still in the game doing relatively the same thing she was doing, what 10 years ago ? And I wonder if her audience changed.
And life (or physics) doesn't stop at nanoseconds. Just think about today CPU's clock speed: 1, 2, 3.. 5 GHz, which means they are working in the sub nanoseconds time range.
Indeed, 1Ghz is a cycle per nano second. But in terms of the videos I have planned, a nanosecond is as far as I need to go.
How about pico - femto - atto - seconds? : ) what is the name of the one at 10 to the power of negative 21?
For the videos I have planned I don't need to talk about anything smaller than a nanosecond.
@@GaryExplains Indeed : )
Shouts out to Grace Hopper.
I know Gregg Jackson uses the term “Nanosecond” a lot.
awesome
You can begin to explain the meaning of a billion and the actual definition of a milliard
So if the population of the globe is 7 billion , me an 6 other people would be nanohumans? Lol
Nanohumanity is this case.
Light travel a second at a shorter distance.
Except for the Letterman clip, I notice that you studiously avoided using 'millionth' or 'billionith.'
I think that millionth and billionth in themselves are hard for people to conceive. Those words alone don't help me understand the duration of a nano second.
@@GaryExplains Thanks for your reply, Gary. If you want to see an amazing demonstration of big numbers check out your fellow RUclipsr's vid: 'The Impossible Hugeness of Deep Time' on the 'It's OK to be Smart' channel. I've watched it and rewatched it many times. I never tire of it. Have a few teacher friends I've referred to it.
Hoppers visual aid did not compute for me.
Where is picosecond
A _thousandth, millionth_ and a _billionth_ of a second, respectively. There. Didn't need a vid. ✌️😉
Hmmm. I hope the video is more than that. Did you watch it?
Nicely done…. But you left out a “shake”.
And half a shake!
Wait a second.
😂
Pico, pico, picochuu...
Nanoseconds is very faster
Who was that lady
Rear Admiral Grace Hopper
Why is his shirt gray one second and black the other? 😂
Magic