Changes

Jump to: navigation, search

Tips for large databases

91 bytes added, 09:43, 3 September 2015
no edit summary
{{out of date|check accuracy}}
Large family tree data files, what to do, and what not to do.
==Loading the file==
For small filesInitial import of a large (100, you 000+) database from either Gramps XML formats or GEDCOM is can work on GEDCOM or GRAMPS XML formattake a few hours. This works greatYou will need to adjust thenumber of allowable locks.For 140,000 people you should use: * ''max_locks'' 300000* ''max_objects'' 300000
However, these formats are completely loaded in your computer memory so, for larger files, The easiest way to do this becomes slow and might bring your computer is to:# create a new Family Tree# exit Gramps# add a '''<code>DB_CONFIG</code>''' file to the database directory before importing (see '''<code>gramps -l</code>''' output for the directory of a standstillspecific family tree.)
Therefore, you should only handle large files by using the GRAMPS GRDB format. You do Contents of this by creating a new GRDB DB_CONFIG file and importing the large file into it. This can take a long time, so do it in the evenings! If you '''enable database transactions''' in the should be: #may want to fiddle with cachesize also {{man menu|Edit->Preferences->General}} menu tab, the importing of data will then be much faster.#set_cachesize 0 200000000 2 set_lk_max_locks 300000Also if you have a file that large it might be prudent to break up file into smaller pieces (i.e. Maternal & Paternal lines in different files, if they are not interrelated) so you only have to use a smaller file. set_lk_max_objects 300000
{{-}}
== Default view: bookmarks and active person ==
As there are many people, loading the person view might take some time. See a comparison of [[GRAMPS Gramps Performance|performance]] on large datasets, between different GRAMPS Gramps versions.
You can circumvent this load time by going to the [[Gramps Relationships Category view screenshot|relationships view]] before opening the grdb filefamily tree. This will open the active person and their family extremely fast, independent of the amount of data you gathered.
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 down enormously.
== Avoid general filters ==
For a surname search:
* click on a person in the [[Gramps People screenshotCategory screenshots|people view]]. Now start typing the family name of the person you need. The view will automatically go to the family name as you complete your typing.
* for a more detailed search, use the keyboard shortcut {{man key press|CTRL|F}}. This will expand all the nodes and allows to search more specifically.
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 "name" on the status bar instead of the "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