Suggest an editImprove this articleRefine the answer for “How do views affect performance?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)Views (VIEW) **don't speed anything up on their own** - they don't store data, they simply **run the saved query** on every access; regular views give no speed boost, but materialized views store the query's result in a physical table and read already-computed data. **Key point:** views exist for **convenience and logic**, not optimization - to actually speed things up, use **indexes**, **caching**, or **materialized VIEWs**.Shown above the full answer for quick recall.Answer (EN)ImageViews (VIEW) **don't speed anything up on their own** - they don't store data, they simply **run the saved query** every time they're accessed. ### What to know So from a performance standpoint: 1. **Regular views (virtual views)** give no speed boost - every `SELECT` from a `VIEW` runs the original SQL query again. If that query is complex (`JOIN`, filters, subqueries), performance suffers accordingly. 2. **Materialized views** are different. They **store the query's result in a physical table**, and the database reads already-computed data. This speeds things up at large volumes, but requires periodic refreshing (`REFRESH`). 3. **Frequently nesting views inside other views** can slow the system down, since the queries stack on top of each other. Bottom line: views exist for **convenience and logic**, not optimization. To actually speed things up, use **indexes**, **caching**, or **materialized VIEWs**.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.