When Optimising Code, Measure

Re:When Optimising Code, Measure by epcoa on Tuesday January 16, 2024 @05:52AM (#39011844)

LOL. The amount of machinery going on under the hood in evaluating those expressions in CPython is staggering. A microscopic detail like a single instruction data dependency has nothing to do with it. (How many CPU add instructions are executed just for those statements? Probably hundreds.)

This is much more likely a quirk of the interpreter (or possibly a fucked up test). CPU details are like 10000 feet down.

[ Parent | on HN ]

Re:When Optimising Code, Measure by reitzensteinm on Tuesday January 16, 2024 @06:00AM (#39011898)

You're absolutely right, but laughing at the notion is unnecessarily rude.

[ Parent | on HN ]

Re:When Optimising Code, Measure by epcoa on Tuesday January 16, 2024 @06:06AM (#39011941)

You’re right. Though it is the scenario in my head playing out of someone slaving over an architecture optimization manual while, zoom out, editing Python that was comical, rather than making fun of anyone specifically.

[ Parent | on HN ]