Performance for Aurora views versus MySql views

I found that MySql scans are one of the most common performance errors, mainly for the reasons mentioned in this.

The biggest flaw is how MySQL handles the view, whether stored or embedded. MySQL will always run a query of the form and materialize the results of this query as a temporary MyISAM

One big drawback of a view is that predicates from an external query NEVER go down into a view

What are the performance differences (if any) for views in Aurora compared to MySql?

Should Aurora representations materialize without considering predicates on an external request?

+5
source share

Source: https://habr.com/ru/post/1233064/


All Articles