Forwarded from Easton Man's Channel (Easton's RSS Bot)
Chips and Cheese
Hot Chips 2025: Session 1 - CPUs
#ChipAndCheese
Hello you fine Internet folks,
Today we are talking about Hot Chips 2025 and specifically the CPU session at Hot Chips 2025 where we had presentations from Condor Computing about their new Cuzco core, PEZY about their upcoming SC4s chip, IBM about their Power11 chip which is already shipping to customers, and Intel about their upcoming E-Core based Xeon CPU codenamed Clearwater Forest.
Hope y'all enjoy!
iframe (www.youtube-nocookie.com)
If you’d like more detailed break downs of most of the chips and the presentations, here are links to our articles on them:
Condor Computing’s Cuzco Core: https://chipsandcheese.com/p/condors-cuzco-risc-v-core-at-hot
PEZY’s SC4s Chip: https://chipsandcheese.com/p/pezy-sc4s-at-hot-chips-2025
IBM Power - What is Next?: https://chipsandcheese.com/p/ibm-power-whats-next
Intel’s Clearwater Forest Xeon: https://chipsandcheese.com/p/intels-clearwater-forest-e-core-server
source
(author: George Cozma)
Hot Chips 2025: Session 1 - CPUs
#ChipAndCheese
Hello you fine Internet folks,
Today we are talking about Hot Chips 2025 and specifically the CPU session at Hot Chips 2025 where we had presentations from Condor Computing about their new Cuzco core, PEZY about their upcoming SC4s chip, IBM about their Power11 chip which is already shipping to customers, and Intel about their upcoming E-Core based Xeon CPU codenamed Clearwater Forest.
Hope y'all enjoy!
iframe (www.youtube-nocookie.com)
If you’d like more detailed break downs of most of the chips and the presentations, here are links to our articles on them:
Condor Computing’s Cuzco Core: https://chipsandcheese.com/p/condors-cuzco-risc-v-core-at-hot
PEZY’s SC4s Chip: https://chipsandcheese.com/p/pezy-sc4s-at-hot-chips-2025
IBM Power - What is Next?: https://chipsandcheese.com/p/ibm-power-whats-next
Intel’s Clearwater Forest Xeon: https://chipsandcheese.com/p/intels-clearwater-forest-e-core-server
source
(author: George Cozma)
🔥1
感觉真的遇到了一个需要用 Effect polymorphism 的东西。考虑写一个 Web service 服务器，handler 有两个版本：Optimize for parallelism 和 optimize for code size
前者 handler 内部的 IO 使用 async runtime 提供的 async io API，后者应该直接使用更贴贴操作系统的 Blocking API
前者 handler 内部的 IO 使用 async runtime 提供的 async io API，后者应该直接使用更贴贴操作系统的 Blocking API
Forwarded from Hacker News (yahnc_bot)
Default musl allocator considered harmful to performance https://nickb.dev/blog/default-musl-allocator-considered-harmful-to-performance/
nickb.dev
Default musl allocator considered harmful (to performance)
In a real world benchmark, the default musl allocator caused a 7x slowdown compared to other allocators. I recommend all Rust projects immediately swap to a different allocator in a musl environment.