Query Efficiency Auditor FAQs

Question 1

Does this skill automatically fix my database queries?

Accepted Answer

No, it follows a 'Report only' rule to ensure safety. It provides detailed locations, severity ratings, and specific recommendations so you can implement the fixes manually.

Question 2

Can I use this for background job optimization?

Accepted Answer

Yes, it specifically checks for inefficient patterns in both API request handlers (High severity) and background jobs (Medium severity) to ensure overall system performance.

Question 3

Is this auditor compatible with all ORMs?

Accepted Answer

While it is tech-stack aware and supports configurations for various databases, it excels with Python/SQLAlchemy patterns by checking settings like expire_on_commit and session scopes.

Question 4

What database patterns does this auditor specifically look for?

Accepted Answer

It searches for redundant entity fetches, N-UPDATE/DELETE loops, unnecessary resolves, over-fetching (loading too many columns), missing bulk operations, and incorrect caching scopes.

Question 5

How does it detect redundant fetches?

Accepted Answer

It traces call chains to identify instances where a function receives an entity ID and fetches the object from the database even though the caller already had the object available.

Query Efficiency Auditor

主要功能

使用场景

Query Efficiency Auditor

主要功能

使用场景