Changes

Jump to: navigation, search

Tips for large databases

14 bytes removed, 03:47, 17 July 2015
Avoid relationship calculation
{{out of date|check accuracy}}
Large family tree data files, what to do, and what not to do.
==Loading the file==
Inital Initial import of a large (100.,000+) database from either gramps format Gramps XML formats or gedcom GEDCOM istiresome and can take a few hours. You will need to adjust thenumber of allowable locks. For 140.,000 people you should use: * ''max_locks'' 300000 and* ''max_objects'' 300000
The easiest way to do this is to:
# create a new Family Tree
# exit grampsGramps# add a '''DB_CONFIG''' file to the database directory before importing (see '''gramps -l''' output for the directory of a specific family tree. )
Contents of this DB_CONFIG file should be:
You can add bookmarks to common people, or in the branch you are researching. This allows to change person in the relationships view without the need to activate the person in the person view first.
 
== Avoid relationship calculation ==
 
Avoid displaying relationships on the status bar. From the {{man menu|Edit > Preferences}} ''Display'' tab change the '''Status bar''' option from {{man label|Relationship to the home person}} to {{man label|Active person's name and ID}}.
== Avoid Gramplets ==
Avoid gramplets which do a lot of database work. The '''[[Deep_Connections_Gramplet|Deep Connections]]''' Gramplet seems to be the worst case. These gramplets slow everything downenormously.
== Avoid general filters ==
Flat person view (list) is faster.
 
== Avoid relationship calculation ==
 
Under the preferences dialog, go the to tab item, and select the option to display the {{man label|name}} on the status bar instead of the {{man label|relationship with the home person}}.
 
== Please contribute ==
 
If you have more tips for working with large databases, please share them here.
[[Category:Documentation]]

Navigation menu