ERP Development3 min read
Odoo 20 Access Rights: Migrating to ir.access
Odoo 20 removes record rules and merges them into access rights with domains. What changed, how to migrate ir.model.access.csv and ir.rule, and what to test.
Service · Run & Improve
ERP performance optimization based on measurement
A slow ERP is not just irritating. When it takes thirty seconds to confirm an order or an MRP run doesn't finish overnight, people find workarounds — and workarounds are where data quality goes to die.
Overview
What erp performance optimization involves
Slowness almost always has a specific cause: a custom computed field recalculating on every read, a report looping over a million records in Python, a missing index, too few worker processes, or an integration hammering the database at peak hours. We find it by measuring.
01The problem
Where things usually go wrong
01
Screens that take seconds to load
List views and forms slow down as data grows, especially those with custom fields.
02
Reports that time out
Month-end reports run for minutes or fail outright.
03
Batch jobs that overrun
MRP, invoicing or sync jobs still running when the morning shift starts.
04
Throwing hardware at it
Bigger servers bought without understanding the bottleneck, with little improvement.
02Our approach
How we handle it
We start by defining what 'slow' means in numbers: which screens, reports and jobs, how long they take, and what acceptable looks like. Then we profile — application-level traces, database query analysis and infrastructure metrics — until the bottleneck is identified with evidence.
Fixes are prioritised by impact. Often a handful of changes — rewriting one computed field, adding two indexes, moving an integration to off-peak batches — deliver most of the improvement. Every change is measured before and after.
03Capabilities
What the work covers
01
Application profiling
Tracing slow requests to the specific code paths responsible.
02
Query optimization
Analysing slow SQL, adding indexes and rewriting expensive queries.
03
Custom code refactoring
Replacing row-by-row loops with batched operations and stored fields.
04
Worker and cache tuning
Configuring application workers, memory limits and caching for your load.
05
Infrastructure right-sizing
Matching CPU, memory and storage to measured demand.
06
Integration scheduling
Moving heavy sync jobs off peak and batching high-frequency updates.
04Technical considerations
Details that decide whether it holds up
01
Representative data
Testing against a production-sized copy, because performance problems rarely appear on small datasets.
02
Database health
Table bloat, vacuum status, connection limits and lock contention reviewed.
03
N+1 patterns
Detection of code that issues one query per record instead of one query per batch.
04
Regression guardrails
Timing benchmarks on critical flows added to the test suite to prevent future slowdowns.
05Process
How the engagement runs
- 01
Measure
Baseline timings for the flows that matter.
- 02
Profile
Identify bottlenecks with traces, query plans and metrics.
- 03
Fix
Targeted changes in priority order.
- 04
Verify
Before/after measurements and regression benchmarks.
06Outcomes
What you should expect afterwards
Faster daily work
Common transactions complete in seconds again.
Reliable batch windows
Overnight jobs finish well before the business day.
Smarter spending
Infrastructure sized to evidence rather than guesswork.
Where it applies
Industries and systems we commonly see
Relevant industries
Relevant integrations
Related services
Often delivered alongside
ERP AuditAn independent health check of configuration, data, custom code, integrations and governance.ERP DevelopmentEngineering for ERP platforms: modules, APIs, reports, portals and performance work.ERP MaintenancePreventive care: updates, backups, security, housekeeping and capacity planning.ERP SupportA named team that knows your configuration, handling issues, questions and small changes.
Insights
Related reading
ERP Development2 min read
Custom ERP vs Off-the-Shelf ERP: How to Decide
When custom ERP development makes sense, when off-the-shelf ERP is the better choice, and why a hybrid — standard core plus custom domain app — is often the answer.
ERP Development2 min read
Odoo Studio vs Custom Code: Where to Draw the Line
What Odoo Studio does well, where it creates trouble, and when to switch to custom module development. A practical decision guide with examples.
FAQ
Frequently asked questions
Will upgrading our server fix the slowness?
Sometimes, but usually not by itself. Most ERP slowness comes from specific code, queries or configuration. Measuring first avoids spending money on hardware that does not address the cause.
How long does a performance review take?
An initial diagnosis typically takes one to three weeks depending on system size and access. Fixes are then scheduled by impact.
Can you optimize systems hosted by a SaaS vendor?
Infrastructure is controlled by the vendor, but custom code, reports, integrations and configuration often account for the slowness and can be fixed.
Next step
Is your ERP slowing the business down?
Send us the three slowest things your team complains about. We will tell you where to look first.