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

Pop_-

no profile record

投稿

We found a bug in the hyper HTTP library

blog.cloudflare.com
163 ポイント·投稿者 Pop_-·20 日前·87 コメント

Rust std fs slower than Python? No, it's hardware

xuanwo.io
687 ポイント·投稿者 Pop_-·3 年前·240 コメント

コメント

Pop_-
·8 か月前·議論
I just scanned through their ToS, "pre-installed with the proprietary Linux OS". Looks not good to me lol.
Pop_-
·2 年前·議論
The github icon on the site directs to the author’s own page, and I couldn’t find any repository for the site, which makes me curious why do they even put the github link? Just for a follow?
Pop_-
·3 年前·議論
I don't know why but this really makes me laugh
Pop_-
·3 年前·議論
Switching to non-default allocator does not always brings performance boost. It really depend on your workload, which requires profiling and benchmarking. But C/C++/Rust and other lower level languages should all at least be able to choose from these allocators. One caveat is binary size. Custom allocator does add more bytes to executable.
Pop_-
·3 年前·議論
It's a known issue for AMD and has been tested by multiple people, and by the data provided by the author. It's fair to pin this problem to AMD.
Pop_-
·3 年前·議論
The root cause is AMD's bad support for rep movsb (which is a hardware problem). However, python by default has a small offset when reading memories while lower level language (rust and c) does not, which is why python seems to perform better than c/rust. It "accidentally" avoided the hardware problem.
Pop_-
·3 年前·議論
It's not stating python is faster than c in general. This is just one very specific case where non-page-aligned memeory reading on AMD is involved.
Pop_-
·3 年前·議論
Disclaimer: The title has been changed to "Rust std fs slower than Python!? No, it's hardware!" to avoid clickbait. However I'm not able to fix the title in HN.
Pop_-
·3 年前·議論
The author has updated the title and also contacted me. But unfortunately I'm no longer able to update it so.