Add /book. Fix ambiguous refs. CSS tweak.

Author: daniel-nichter

config.toml

@@ -4,6 +4,10 @@ title = "Hack MySQL"
 disqusShortname = "hackmongo"
 copyright = "2024 Daniel Nichter"
 
+[services]
+  [services.disqus]
+    shortname = 'hackmongo'
+
 [params]
   [params.author]
     name = 'Daniel Nichter'

content/announcing-finch-mysql-benchmarking.md

@@ -166,7 +166,7 @@ And it's all extensively documented: https://square.github.io/finch/
 
 Benchmarking is difficult, even for experts.
 But ideally it's something software developers can do and actually do.
-To help make that reality is another reason why I wrote Finch&mdash;and the page [Benchmarking]({{< ref "benchmarking" >}}).
+To help make that reality is another reason why I wrote Finch&mdash;and the page [Benchmarking]({{< ref "eng/benchmarking" >}}).
 
 I've already seen it in action once: where I work, a team of software engineers used Finch to recreate the critical part of their app's workload.
 They benchmarked one database environment versus another and found the other had latency the app couldn't handle.

content/book.md

@@ -0,0 +1,22 @@
+---
+date: "2024-11-09T14:27:00-05:00"
+title: "Efficient MySQL Performance In 10 Sentences"
+tags: ["mysql", "book"]
+---
+
+Don't have time to read [_Efficient MySQL Performance_](https://oreil.ly/efficient-mysql-performance)?
+Here's the book (10 chapters) in one-liners.
+
+1. Performance is query response time.
+2. Proper left-most indexing is required for performance.
+3. The less data, the better.
+4. Access patterns (part of the workload) help or hinder performance.
+5. Sharding is how to scale writes when single-node performance is truly reached.
+6. Server metrics reflect how the app workload causes MySQL to work.
+7. Replication lag is data loss.
+8. Locks are held until a transaction commits, so commit quickly.
+9. There are many other challenges that you might need to address—sorry.
+10. MySQL in the cloud is slower _and_ more expensive, so performance is more important than ever.
+
+
+

content/rand/response-time-slo.md

@@ -8,14 +8,14 @@ alaises:
   - /post/response-time-sla/
 ---
 
-Response time [percentiles]({{< ref "percentiles" >}}) are a ubiquitous measure of system performance.
+Response time [percentiles]({{< ref "eng/percentiles" >}}) are a ubiquitous measure of system performance.
 The P999 (99.9th percentile) is a high bar, so it's a good metric to determine a service level objective (SLO).
 For example, my team runs a system with a P999 &leq; 800 millisecond SLO.
 The system meets the SLO, but here's its P999 graph:
 
 ![Query SLO P999 Chart](/img/query-sla-p999-chart.png)
 
-Looks bad, but the system _is_ meeting the SLO. To understand why, let's look at how percentiles are calculated. The [Percentiles]({{< ref "percentiles" >}}) page on this site is a longer, more technical read about the subject, but for our purposes here the TL;DR is: <mark>a percentile is a high water mark.</mark> Consider a literal high water mark:
+Looks bad, but the system _is_ meeting the SLO. To understand why, let's look at how percentiles are calculated. The [Percentiles]({{< ref "eng/percentiles" >}}) page on this site is a longer, more technical read about the subject, but for our purposes here the TL;DR is: <mark>a percentile is a high water mark.</mark> Consider a literal high water mark:
 
 ![High water mark (Lake Mead) Source: durangoherald.com](/img/high-water-mark.jpg)
 

layouts/partials/disqus.html

@@ -1,5 +1,5 @@
 {{ if (.Params.comments) | or (and (or (not (isset .Params "comments")) (eq .Params.comments nil)) (.Site.Params.comments)) }}
-  {{ if .Site.DisqusShortname }}
+  {{ if .Site.Config.Services.Disqus.Shortname }}
     <div class="comments">
       {{ template "_internal/disqus.html" . }}
     </div>

src/hackmysql.css

@@ -173,7 +173,7 @@ h2 + .note {
   border-color: red;
   text-align: justify;
 }
-.warn > a { color:black; text-decoration:none; }
+.warn > a, a:has(.figure) { color:black; text-decoration:none; }
 .left-icon {display:flex; align-items:center;}
 .left-icon > img {float:left; margin-right:1rem;}
 .note.warn.left-icon {padding-left: 1rem;}