16,737
edits
Changes
→Optimizations for big databases
The report was tested with a [[Gramps_Performance#Genealogical_datasets|database over 120,000 people]] without blocking issue.
The technology used for this report (client-side Javascript) is not designed for managing big amounts of data.
This could lead to performance issues, for databases over 5000 people, when the configuration is not properly set. The following tunings could be used:
* The optional index columns should be discarded
* The indexes should be displayed as lists and not as tables
Another possility possibility is to use only a portion of the Family Tree database. Generating the report with a smaller filter enhances the performances and provides a smoother experience for the Web site users.
{{man warn|Do you really want to use the entire Family Tree database ?|Be aware that if you select the '''Entire Database''' filter option for your Family Tree database that very big files will be generated (depending on the size of your Family Tree database). It is recommended to start with a smaller filter (for example: ancestors of a certain person) to simplify the output while you learn about the Dynamic Web report.}}
Moreover, when rendering large datasets, the report disables some fancy features for better performances.
== <span id="Help">Help for the Web site users</span> ==