<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Computer-Architecture on Tee Zhi Yao</title><link>https://teezhiyao.com/tags/computer-architecture/</link><description>Recent content in Computer-Architecture on Tee Zhi Yao</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 01 May 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://teezhiyao.com/tags/computer-architecture/feed.xml" rel="self" type="application/rss+xml"/><item><title>OMSCS: CS 6290 High Performance Computer Architecture (Spring 2025)</title><link>https://teezhiyao.com/posts/omscs-cs-6290-high-performance-computer-architecture-spring-2025/</link><pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate><guid>https://teezhiyao.com/posts/omscs-cs-6290-high-performance-computer-architecture-spring-2025/</guid><description>&lt;p>CS 6290 was one of those courses where I came out knowing exactly how a processor works under the hood in a way I hadn&amp;rsquo;t before. It covers the full stack of modern processor design — from the simplest pipelining all the way up to multi-core coherence protocols and memory consistency models. It&amp;rsquo;s dense, quantitative, and rewards meticulous attention to detail.&lt;/p>
&lt;h2 id="what-the-course-covered">What The Course Covered&lt;/h2>
&lt;p>The course followed a logical arc that built up in complexity. It started with fundamental metrics — the Iron Law of Performance (execution time = instruction count × CPI × cycle time) and Amdahl&amp;rsquo;s Law, which became the recurring mental models for evaluating every design tradeoff.&lt;/p></description></item></channel></rss>