Best Practices for Managing Custom Fields and Performance in Large EspoCRM Instances

[adrianNove]

Hi all,

I have been working with EspoCRM on a growing database and I noticed that as we add more custom fields and relationships. the system can become a bit slower over time.

I wanted to ask how others are managing this in a clean and efficient way. For example do you regularly review and remove unused fields or is there a better method to keep things optimized? Also are there any recommended practices when designing entities at the beginning to avoid performance issues later?

It would be helpful to hear how people handle structure, indexing or any small steps that make a big difference in long-term usage.

Thanks in advance.

[victor]

- Try not to create unnecessary fields, relationships and entities.
- Periodically do Hard Rebuild: https://docs.espocrm.com/administrat.../#hard-rebuild.
- Delete unnecessary tables via phpMyAdmin or its analogues.
- Check Administration > Settings > General > Clean up deleted records.

[yuri]

Unchecking deleted records cleanup is not needed.

[victor]

Last point changed

[yuri]

With growing database adding custom indexes becomes a necessity. https://docs.espocrm.com/administrat...tabase-indexes.

Anything else is the same as with any other database. Databases tend to slow down as they grow. To compensate it, allocating more hardware resources, tweaking and indexing are needed.