Understanding LLM Inference Bottlenecks

[!NOTE] This is example content. Replace this folder with a real article when ready; it exists to document and exercise the blog format.

Each article lives in its own folder under content/blog/. The folder contains a README.md and may contain a local cover or other article media:

content/blog/
└── understanding-llm-inference-bottlenecks/
├── README.md
└── cover.svg

The folder name creates the stable route: /blog/understanding-llm-inference-bottlenecks. An explicit lowercase slug can be added to frontmatter when a route must remain independent of the folder name.

Frontmatter is the article contract

Every README.md begins with validated YAML metadata. Dates use YYYY-MM-DD, category is one of work, personal, or passion, and tags use lowercase slugs.

FieldRequiredPurpose
titleYesArticle and metadata title
descriptionYesSearch, cards, and page metadata
publishedYesPublication order and RSS date
updatedNoShown when different from publication
categoryYesPrimary blog section
tagsYesRelated posts and filters
draftNoExcluded from production when true
featuredNoEligible for featured placement
coverNoPath relative to the article README
cover_altWith coverDescribes a meaningful cover

The validator rejects impossible dates, duplicate tags or slugs, unknown categories, missing local media, and covers without descriptive alternative text.

Markdown features

Articles support GitHub-flavored Markdown and MDX where it adds real value:

  • Tables, task lists, nested lists, and blockquotes
  • Footnotes and links
  • Heading anchors
  • Inline code and highlighted code fences
  • Responsive images and tables
// Fenced code is highlighted by the site build.
double bandwidth_gb_s(double bytes, double seconds) {
return bytes / seconds / 1'000'000'000.0;
}

Images in the article body use normal Markdown and must include useful alt text:

![Chart comparing measured memory bandwidth across configurations](./bandwidth.webp)

Empty alt text is reserved for truly decorative images. The content validator warns about empty Markdown alt text so that intent is reviewed.

Publishing workflow

  1. Create a named folder with README.md.
  2. Add and validate frontmatter.
  3. Write the article and keep media beside it.
  4. Run pnpm validate.
  5. Preview locally and set draft: false when it is ready.

Reading time, category and tag data, related posts, previous/next navigation, RSS metadata, and the article URL are derived at build time.1

Footnotes

  1. The final website is statically generated for GitHub Pages.