86
edits
Changes
→Optimizations for big databases
=== Optimizations for big databases ===
The report was tested with a [[Gramps_Performance#Genealogical_datasets|database over 120,000 people]] without blocking issue.
<br/>Nevertheless, some users could have performance issues.
The technology used for this report (client-side Javascript) is not designed for managing big amounts of data.
* The optional index columns should be discarded
* The indexes should be displayed as lists and not as tables
Another possility is to use only a portion of the Family Tree database. Generating the report with a smaller filter (for example: ancestors of a certain person) enhances the performances and provides a smoother experience for the Web site users.
Moreover, when rendering large datasets, the report disables some fancy features for better performances.
== <span id="Help">Help for the Web report users</span> ==
