# Denormalization

> Storing the same fact in more than one place, or keeping a pre-joined copy, so a read need not join or compute it. Reads get cheaper, and every write has to update each copy.

Data

## In Quorum

Denormalization research makes each Database read cost 30% less CPU and each write 20% more (10). It pays on a read-heavy Design and hurts a write-heavy one, which is the trade the Tradeoff card’s preview shows before the player takes it.

## Design

[Performance track](https://wiki.playquorum.dev/design/10-progression.md#track-performance)

## Read next

[N+1 query](https://wiki.playquorum.dev/glossary/n1-query.md), [Cache hit rate](https://wiki.playquorum.dev/glossary/cache-hit-rate.md), [OLTP and OLAP](https://wiki.playquorum.dev/glossary/oltp-and-olap.md), [Eventual consistency](https://wiki.playquorum.dev/glossary/eventual-consistency.md)

## Learn more

- [Wikipedia: Denormalization](https://en.wikipedia.org/wiki/Denormalization)

## See also

- [Glossary](https://wiki.playquorum.dev/glossary.md)

Source: https://wiki.playquorum.dev/glossary/denormalization