HackerTrans
トップ新着トレンドコメント過去質問紹介求人

itamarst

5,606 カルマ登録 10 年前
I write about speeding up Python software development, and code, at https://pythonspeed.com

I write about fundamental engineering skills and programmer career advice at https://codewithoutrules.com

I also write a weekly email about all the mistakes I've made both coding and in my career over the past 20 years, so that you can learn and avoid them: https://softwareclown.com

投稿

[untitled]

1 ポイント·投稿者 itamarst·3 か月前·0 コメント

[untitled]

1 ポイント·投稿者 itamarst·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 itamarst·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 itamarst·6 か月前·0 コメント

Testing the compiler optimizations your code relies on

pythonspeed.com
1 ポイント·投稿者 itamarst·10 か月前·0 コメント

The cold incubator: the VC dream of workerless wealth

codewithoutrules.com
1 ポイント·投稿者 itamarst·4 年前·0 コメント

コメント

itamarst
·10 時間前·議論
Better guesses reduce the number of guesses, so there will be less branch misprediction, but there will still be mispredictions for each remaining branch. So I would guess branchless interpolation search would still help.

In practice because the real code in scikit-learn is used in parallel, memory bandwidth starts being a problem in real usage. Plus, in the overall algorithm (this is just a small part) the time spent on binary search is now low enough that there are other, more significant bottlenecks elsewhere. So in practice the branchless optimization had enough impact on the original motivating code base that there didn't seem much point spending more time on it.