Table of Contents

Introduction Installation Projects Tables Inserts Searches Updates Deletes CLI Good Practices Conclusion

Good Practices - Flaarum Tutorials

  1. For a write-heavy database like a mailbox; do not have a single table. Splitting into many tables would improve the speed of the insertion.
    This is due to mutexes (avoid race conditions in multithreaded environment) and creation of indexes (indexes speed up searches).

  2. Do your data validation on the front end (web app or GUI). This is because databases do not autoscale and is a generally faster approach.

  3. Put a limit of the number of rows on every search. This would reduce your RAM usage.

  4. Backup your database as CSV or JSON files monthly for safety sake.

  5. To import into your flaarum installation use flaarum.prod. It results to alot of speed gain.

  6. If you feel flaarum searches are failing and you have the data. Use the command flaarum.prod ridx to reindex your table. This could occur after changes in a field nindex attribute.

< Previous Next >