How to Speed up a Python Program 114,000 times. on HackerTube: recommended by 3 Hacker News commenters across 3 separate months, 2015–2022.
talk · intermediate · evergreen
David Schachter describes how he made a data-collection Python program run 114,000 times faster, drawing on decades of experience. The talk covers pipelining, cache effects and other optimization lessons.
A favorite tech talk on HN for showing that hardware knowledge and generalist skills beat simply adding machines.
“Humour, serious technical insight and a good reminder of why being a generalist is an advantage.”
5 Hacker News comments link this video. Each one links back to its thread.
"How to Speed up a Python Program 114,000 times." - ▶ this video Humour, serious technical insight and a good reminder of why being a generalist is an advantage.
in “Ask HN: What's your favorite tech talk?” · View on HN
I thought this was going to be "How to Speed up a Python Program 114,000 times"[0]. It's an hour-long talk, but quite enjoyable. In the example in the talk, it was less about knowing cs algorithms and more about knowing the details of how modern computer architecture works, but the lesson is the same: sometimes the background knowledge of a cs degree is useful. He also has the same point about optimizing our code rather than just adding more and more machines. [0] ▶ this video
in “14,000x Speedup (2015)” · View on HN
This will technically only work on pipelined architectures of which all major CPU architectures are one. You will be able to see a significant boost to performance given the following are all true: * You have no inter dependancy of information across the lines * All your data is in the cache * You don't have instructions generated between the two lines that will require some sort of operand forwarding Basically, if you already have the stuff in the cache, the calculation is invarent to the last calculation, and you have a processor capable of it you'll see a large speed improvement. There is a great talk about this [0] (for the exact moment go to [1]). If you're interested further I'd very much recommend finding some sort of GOOD computer architecture class. Luckily now we have a fantastic resource to locate these such courses [2]. This seems like dark magic and many programmers refuse to come to terms with it's existence. Check out `dreta`'s comment to see an example. Now I do agree with dreta, this is VERY much architecture dependant but most architectures would benifit from this sort of optimization. Pretty much all modern Intel and AMD CPU's caches are large enough, they support a big enough cache, and they also all have pipelines under the hood. Intel started this in the pentium series with a 5-stage-pipeline (which I find very funny due to the GHz wars that came from that time period desipte the pipeline being probably the pargest performance boon in most cases that you
in “Talks that changed the way I think about programming” · View on HN
> I remember I recently saw a lecture by an industry professional who took a Python algorithm and improved it 100 000x, in parts. That is, in stages he explained how to utilize the hardware on that particular machine, to improve the algorithm so much that it was hard to believe. Anyone have a link? I suspect it's this one: ▶ this video
in “JavaScript Containers” · View on HN
An example of "scaling in" is this talk, "How to speed up a Python program 114,000 times": ▶ this video
in “The Cost of Scalability in Graph Processing” · View on HN