---
title: "Discussion on \"One index, 64× faster: what a composite index actually does\" | Hashnode"
description: "Discussion on \"One index, 64× faster: what a composite index actually does\". A query summing one customer's payments took 1,086 ms. After adding one index, the same query took 17 ms.\nThe query didn't change. What changed was how MySQL could find the rows. Here's what happened"
url: "https://hashnode.com/posts/one-index-64-faster-what-a-composite-index-actually-does/6acd21d2c8dd9b1bef876d43"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [One index, 64× faster: what a composite index actually does](https://kevingakio.hashnode.dev/one-index-64-faster-what-a-composite-index-actually-does?utm_source=hashnode&utm_medium=feed)

A query summing one customer's payments took 1,086 ms. After adding one index, the same query took 17 ms. The query didn't change. What changed was how MySQL could find the rows. Here's what happened

Oct 12 · 5 min read · kevingakio.hashnode.dev  
Read the article

-   [#database-performance-sql-backend](https://hashnode.com/tag/database-performance-sql-backend)
-   [#indexing-strategy](https://hashnode.com/tag/indexing-strategy)
-   [#performance-optimization](https://hashnode.com/tag/performance-optimization)

## Written by

[Kevin gakio](https://hashnode.com/@kevin1146)

@kevin1146

  
[View profile](https://hashnode.com/@kevin1146)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
