Re:Google cuts jobs at cloud-computing group
by basementcat on Friday February 14, 2020 @07:01PM
(#22331728)
If you assemble a 9+ stage pipeline, you may reach a point where you produce approximately one baby each month.
[ Parent
| on HN ]
Re:Google cuts jobs at cloud-computing group
by phkahler on Friday February 14, 2020 @07:16PM
(#22331824)
Even then they are "working" independently. It's not a pipeline that passes the baby from one to the next. That's just plain parallelism. Either way it would do nothing to latency and so would not get the current one done any sooner.
Re:Google cuts jobs at cloud-computing group
by manigandham on Friday February 14, 2020 @07:45PM
(#22332035)
That's not a 9 stage pipeline, it's 9 separate single stage pipelines.
Re:Google cuts jobs at cloud-computing group
by bobsil1 on Friday February 14, 2020 @10:51PM
(#22333100)
Massively parallel Baby Processing Units (BPUs)
Re:Google cuts jobs at cloud-computing group
by joejerryronnie on Friday February 14, 2020 @11:35PM
(#22333287)
If you implement QBPUs (Quantum Baby Processing Units), you could theoretically produce infinite babies. Of course, we're perpetually 10 years away from working QBPUs.
Re:Google cuts jobs at cloud-computing group
by znpy on Friday February 14, 2020 @07:27PM
(#22331900)
That's throughput, not latency.
Re:Google cuts jobs at cloud-computing group
by majormajor on Friday February 14, 2020 @07:41PM
(#22332003)
Most companies have more things they want to do then they can do in the next 6 months. So if you increase throughput without latency, you can still get more of those projects done. Even if you're still doing them all inefficiently.
It's ugly, but "don't hire more people because we'll be less efficient" often runs into this ugly "but we need more total output, not more efficiency" wall.
Re:Google cuts jobs at cloud-computing group
by blattimwind on Friday February 14, 2020 @08:47PM
(#22332494)
Yes, that's exactly the point of pipelining.