Skip to content

Commit 9f2c9e9

Browse files
authored
fix(blog): colours are wrong (#4763)
(From the Latency/SLO improvement blog post) This is bothering me. The colours in the text do not match the colours in the graph.
1 parent 4eb7a06 commit 9f2c9e9

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • gcp/website/blog/content/posts/api-latency-improvements-and-revised-slos

gcp/website/blog/content/posts/api-latency-improvements-and-revised-slos/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ This change is now fully rolled out to production, and the impact on API latency
3131

3232
On average, the `GET /v1/vulns/{id}` endpoint is 5x faster, `POST /v1/query` is 2.5x faster, and `POST /v1/querybatch` is 3x faster.
3333

34-
In terms of percentiles, you can see our P50 (blue), P90 (green), and P95 (purple) latencies below:
34+
In terms of percentiles, you can see our P50 (blue), P90 (yellow), and P95 (red) latencies below:
3535
![Line graph of GET /v1/vulns/{id} latency percentiles, comparing the higher 'before' state (dashed lines) to the significantly lower 'after' state (solid lines).](getvulnbyid_percentiles.png "P50/P90/P95 latencies for GET /v1/vulns/{id} before (dashed) and after (solid), showing a significant drop.")
3636
![Line graph of POST /v1/query latency percentiles, comparing the higher 'before' state (dashed lines) to the significantly lower 'after' state (solid lines).](queryaffected_percentiles.png "P50/P90/P95 latencies for POST /v1/query before (dashed) and after (solid), showing a significant drop.")
3737
![Line graph of POST /v1/querybatch latency percentiles, comparing the higher 'before' state (dashed lines) to the significantly lower 'after' state (solid lines).](queryaffectedbatch_percentiles.png "P50/P90/P95 latencies for POST /v1/querybatch before (dashed) and after (solid), showing a significant drop.")

0 commit comments

Comments
 (0)