Why Odoo Feels Slow After 6 Months (15-Minute Checks We Run First)

Introduction

Six months after go-live, Odoo often feels fine in the morning and painful by afternoon. Users blame "the upgrade," the network, or a new module. In most cases the database is doing too much work with too little visibility—cron overlap, missing indexes, or a handful of heavy queries—not a broken ERP.

These are the checks we run first on a production instance. They take about fifteen minutes and need no new modules.

What we check first

1. Cron queue — In Settings → Technical → Automation → Scheduled Actions, look for jobs stuck in "Running" or firing every minute.
2. Long-running SQL — On PostgreSQL, pg_stat_activity with queries over 30 seconds.
3. Worker / process count — Check Odoo logs for MemoryError or frequent worker respawns.
4. Attachment and filestore growth — Bloated ir_attachment slows every form with images or PDFs.
5. Custom modules on hot paths — Bad write() overrides on sale.order, stock.picking, account.move.
6. Mail and chatter — Mass mailing spikes on high-volume records.
7. Reporting in peak hours — Move pivot exports and PDF batches to quiet windows.

Quick wins vs deeper fixes

Quick wins: Reschedule noisy crons, add indexes, archive old attachments, cap concurrent report jobs.

Deeper fixes: EXPLAIN ANALYZE tuning, read replicas for reporting, right-sizing workers after measuring concurrency.

For full production depth, see the Odoo Survival Guide PDF.

• Odoo modules
• Engineering eBooks