database-performance

To fix N+1 query patterns in Django ORM Canvas plugins, apply select_related for foreign keys and prefetch_related for reverse relations to optimize data access in plugin handlers during code reviews.

Query profiling optimizations use select_related for foreign key relations via SQL joins, while prefetch_related handles reverse relations with separate queries to mitigate N+1 patterns in Canvas plugin data loading.

Run a pre-deployment performance audit checklist during code reviews to identify N+1 patterns in Canvas SDK data models, applying select_related and prefetch_related where appropriate to guide optimization decisions.

Yes, this performance optimization skill works with standard Django ORM patterns in Canvas plugins, enforcing best practices for select_related and prefetch_related using reference guidance from performance_context.txt.

The best way to eliminate N+1 queries in Canvas plugin handlers is profiling data access and using Django ORM methods like select_related for foreign keys and prefetch_related for reverse relations.

You should not use select_related for reverse relations or many-to-many fields; use prefetch_related instead to execute separate queries and avoid expensive database joins in Canvas plugin performance auditing.