<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Akeel Ather Medina</title><link>https://akeelmedina22.github.io/posts/</link><description>Recent content in Blog on Akeel Ather Medina</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 15 Oct 2026 00:00:00 +0500</lastBuildDate><atom:link href="https://akeelmedina22.github.io/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Seeing Timbre: Ryuichi Sakamoto</title><link>https://akeelmedina22.github.io/posts/timbre/</link><pubDate>Thu, 15 Oct 2026 00:00:00 +0500</pubDate><guid>https://akeelmedina22.github.io/posts/timbre/</guid><description>&lt;p>I&amp;rsquo;ve been wanting to make a post about music for a long time. I&amp;rsquo;m not the best writer though, but I think about music often. Specifically, I&amp;rsquo;ve been interested in a few pieces by Ryuichi Sakamoto. They&amp;rsquo;re all unique in their own way, and at first I wanted to explore the phenomenon of his composition to describe a real object. For example, give a listen to Obsidian from Crystalline. It &lt;em>sounds&lt;/em> like Obsidian. I don&amp;rsquo;t have the words to describe how that is. So, I&amp;rsquo;ve tried to turn some of his songs into images. For this post, I&amp;rsquo;ve used these:&lt;/p></description></item><item><title>Reflections on my MSc Thesis</title><link>https://akeelmedina22.github.io/posts/thesis/</link><pubDate>Fri, 11 Sep 2026 00:00:00 +0500</pubDate><guid>https://akeelmedina22.github.io/posts/thesis/</guid><description>&lt;p>I completed my MSc thesis on the 22nd of August, and left Edinburgh on the 26th. Everything went by in a blur, after a life changing year abroad. Today is the 11th of September, it&amp;rsquo;s been just over 2 weeks, and I wanted to write a short reflection piece. You can read my thesis if you&amp;rsquo;re interested in profiling KV cache offload, I&amp;rsquo;ll be making it available as soon as it is graded.&lt;/p></description></item><item><title>Reflections on ISC SCC 2026</title><link>https://akeelmedina22.github.io/posts/scc-2026-inference/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0500</pubDate><guid>https://akeelmedina22.github.io/posts/scc-2026-inference/</guid><description>&lt;p>As a participant representing TeamEPCC in the ISC Student Cluster Competition 2026, I&amp;rsquo;ve recently had the chance to work on a custom-built HPC cluster that we shipped to Hamburg for the in-person competition. I wanted to give my overall reflections on the competition and my experience.&lt;/p>
&lt;p>The SCC has never included llama.cpp as a micro-benchmark, usually focusing on HPC-specific benchmarks like HPL and HPCG. This year introduced llama.cpp, which allows LLM inference with minimal setup on a wide range of hardware. It is a plain C/C++ implementation with no dependencies. It runs surprisingly well on Apple silicon! Understanding how to use llama.cpp is fairly simple, but maximizing performance for specific hardware could be a whole MSc thesis. The source code is very well written, and it is easy to find and read specific implementations of custom kernels. But the majority of performance comes from tuning the runtime parameters, so understanding the workload, and how those parameters change the character of your problem on your hardware, is what actually matters. That makes it quite different from the other benchmarks we were given, like HPL.&lt;/p></description></item><item><title>C++ Design Patterns</title><link>https://akeelmedina22.github.io/posts/cpp-design-patterns/</link><pubDate>Thu, 05 Jun 2025 19:11:23 +0500</pubDate><guid>https://akeelmedina22.github.io/posts/cpp-design-patterns/</guid><description>&lt;p>Based on the following repository - &lt;a href="https://github.com/AkeelMedina22/cpp-design-patterns">cpp-design-patterns&lt;/a>&lt;/p>
&lt;h2 id="background">Background&lt;/h2>
&lt;p>I was recently browsing &lt;a href="https://github.com/amdazm05/libtransform.cc">this&lt;/a> repository on Github, and was inspired to do something similar. I hadn&amp;rsquo;t written C++ in over 2 years, since taking a course in GPU-Accelerated Computing. But, with my Masters starting in a few months, I decided to start looking in to Modern C++. I noticed this library had some interesting usage of &lt;code>static&lt;/code>, and it was the first thing I wanted to investigate. I went down a rabbit hole of the static-initialization order, &lt;a href="https://www.youtube.com/watch?v=IMZMLvIwa-k&amp;amp;list=LL&amp;amp;index=19">this&lt;/a> video by The Cherno (I got through my course on OOP 5 years ago because of him!), and Scott Meyers&amp;rsquo; &lt;em>Effective C++&lt;/em> (Item 4), where the Meyers Singleton originates, alongside the Factory Creational Pattern.&lt;/p></description></item><item><title>Understanding Simultaneous Multithreading (SMT)</title><link>https://akeelmedina22.github.io/posts/smt/</link><pubDate>Tue, 06 May 2025 00:00:00 +0500</pubDate><guid>https://akeelmedina22.github.io/posts/smt/</guid><description>&lt;p>While reading &lt;em>Performance Analysis and Tuning on Modern CPUs&lt;/em> by Denis Bakhvalov, I had a surprising realization. Before this book, I had a completely incorrect understanding of what a thread is. Somewhere in my mental model of CPU microarchitecture, the &amp;ldquo;thread&amp;rdquo; was a muddy concept that vaguely correlated to a physical core, but it was more of an abstraction. I never interacted much with them because of Python&amp;rsquo;s Global Interpreter Lock (GIL), well-known for nulling any performance gain from SMT in compute-bound workflows, which was my main use case.&lt;/p></description></item></channel></rss>