入门文章系列：
在探讨大语言模型（LLM）的性能时，一个流传已久的说法是：“解码过程中的 Attention 操作是访存密集型（Memory Bound）的。” 这个观点深入人心，以至于许多优化讨论都以此为前提。然而，随着模型架构的演进和解码策略的创新，这一迷思正在被打破。
https://shinezyy.github.io/ArchShineZ/post/decoding-myth/
在探讨大语言模型（LLM）的性能时，一个流传已久的说法是：“解码过程中的 Attention 操作是访存密集型（Memory Bound）的。” 这个观点深入人心，以至于许多优化讨论都以此为前提。然而，随着模型架构的演进和解码策略的创新，这一迷思正在被打破。
https://shinezyy.github.io/ArchShineZ/post/decoding-myth/
ShineZ's Homepage
The myth of decoding large language models | ShineZ's Homepage
在探讨大语言模型（LLM）的性能时，一个流传已久的说法是：“解码过程中的 Attention 操作是访存密集型（Memory Bound）的。” 这个观点深入人心，以至于许多优化讨论都以此为前提。然而，随着模型架构的演进和解码策略的创新，这一迷思正在被打破。
dramforever's blog
dram.page is now served by grebedoc.dev
That’s it. If you’re seeing this post, your receiving this page from grebedoc.dev.
Check it out if you want a way to serve the contents from a git repo over HTTP(S) on the public Internet.
The backend server on grebedoc.dev is called git-pages. I’ll probably use the two names interchangably for the rest of this article.
(However, I will use “
Zero downtime migration
I think I’ve managed to do a zero-downtime migration from Netlify. This is what I did:
First, I moved everything to the
Then, I set up the “method 1” DNS record:
Then, I triggered an initial clone using the
This has two effects:
● It asks git-pages to start serving files for
● It registers
Now I can see if it’s serving my pages correctly:
For me, that looked good, so I’m ready to do the switch, changing the actual DNS record to make my site point to the grebedoc.dev server:
… well,
And that’s it, I’m serving the latest site on grebedoc.dev.
As for auto-updating, the webhook part works normally.
What’s wrong with Netlify?
Nothing, really, but since I use zero complex features and just serve what’s in the git repo, this is just simpler.
source
dram.page is now served by grebedoc.dev
That’s it. If you’re seeing this post, your receiving this page from grebedoc.dev.
Check it out if you want a way to serve the contents from a git repo over HTTP(S) on the public Internet.
The backend server on grebedoc.dev is called git-pages. I’ll probably use the two names interchangably for the rest of this article.
(However, I will use “
grebedoc.dev” to specifically refer to the domain itself, and use grebedoc.dev to refer to the service.)Zero downtime migration
I think I’ve managed to do a zero-downtime migration from Netlify. This is what I did:
First, I moved everything to the
pages branch. This is just easier.Then, I set up the “method 1” DNS record:
_git-pages-repository.dram.page. 600 IN TXT (
"https://github.com/dramforever/dram.page.git" )Then, I triggered an initial clone using the
PUT method.$ curl -v -X PUT -H 'Host: dram.page' \
'https://grebedoc.dev' \
--data 'https://github.com/dramforever/dram.page.git'This has two effects:
● It asks git-pages to start serving files for
Host: dram.page● It registers
dram.page as a known domain to git-pages, allowing it to immediately start receiving HTTPS requests. This lets me to completely avoid sending anything over unencrypted HTTP, including the webhook.Now I can see if it’s serving my pages correctly:
$ curl -v -H 'Host: dram.page' 'https://grebedoc.dev'For me, that looked good, so I’m ready to do the switch, changing the actual DNS record to make my site point to the grebedoc.dev server:
dram.page. 600 IN ALIAS grebedoc.dev… well,
ALIAS is not a real DNS record. The effect is that the authoritative DNS server looks up the IPv4 and IPv6 address of the domain grebedoc.dev and serves them as A and AAAA records of dram.page. Fortunately my authoritative DNS service has this feature.And that’s it, I’m serving the latest site on grebedoc.dev.
As for auto-updating, the webhook part works normally.
What’s wrong with Netlify?
Nothing, really, but since I use zero complex features and just serve what’s in the git repo, this is just simpler.
source
Chips and Cheese
Everactive’s Self-Powered SoC at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Everactive’s Self-Powered SoC at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Chips and Cheese
AMD’s RDNA4 GPU Architecture at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
AMD’s RDNA4 GPU Architecture at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
中国防火长城（GFW）今日发生史上最大规模的内部文档泄漏。超过500GB的源代码、工作日志与内部交流记录外泄，揭示了GFW的研发与运作细节。
泄漏源自GFW核心研发力量之一的积至公司（首席科学家方滨兴）及中科院信息工程研究所第二研究室的处理架构组 MESA Lab。该公司不仅为新疆、江苏、福建等地政府提供服务，还在“一带一路”框架下向缅甸、巴基斯坦、阿塞俄比亚、哈萨克斯坦等国输出审查与监控技术。
该泄漏事件意义重大且深远，由于资料体量庞大，GFW Report 将持续分析并在此页面更新：
https://gfw.report/blog/geedge_and_mesa_leak/zh/
泄漏源自GFW核心研发力量之一的积至公司（首席科学家方滨兴）及中科院信息工程研究所第二研究室的处理架构组 MESA Lab。该公司不仅为新疆、江苏、福建等地政府提供服务，还在“一带一路”框架下向缅甸、巴基斯坦、阿塞俄比亚、哈萨克斯坦等国输出审查与监控技术。
该泄漏事件意义重大且深远，由于资料体量庞大，GFW Report 将持续分析并在此页面更新：
https://gfw.report/blog/geedge_and_mesa_leak/zh/
Chips and Cheese
Intel’s E2200 “Mount Morgan” IPU at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Intel’s E2200 “Mount Morgan” IPU at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
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)
Daniel Lemire's blog
Splitting a long string in lines efficiently
source
Splitting a long string in lines efficiently
source
Daniel Lemire's blog
Splitting a long string in lines efficiently
Suppose that you have a long string and you want to insert line breaks every 72 characters. You might need to do this if you need to write a public cryptographic key to a text file. A simple C function ought to suffice. I use the letter K to indicate the…
Chips and Cheese
Liquid Cooling Exhibits at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Liquid Cooling Exhibits at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
