Jump to: navigation, search

Tips for large databases

1,047 bytes added, 03:27, 20 October 2020
Avoid Gramplets
{{man tip|The advice on this page was for older versions of Gramps so may not work for you. Please update as needed.}}{{stub}}<!--check accuracy / Incorporate "Import tested with the GRANDMA Mennonite database of 1.4 million people. by user on reddit!! " --> Large family tree data files, what to do, and what not to do.
==Loading the file==
[[Image:EditPreferencesGeneral226.png{{man note|thumb|General tab Should work for BSDDB versions of Edit->Preferences dialog box]]Gramps}}For small filesInitial import of a large (100, you 000+) database from either Gramps XML formats or GEDCOM can work on GEDCOM or GRAMPS XML formattake a few hours. This works greatYou will need to adjust the number of allowable locks.For 140,000 people you should use: However, these formats are completely loaded in your computer memory so, for larger files, * ''max_locks'' 300000* ''max_objects'' 300000 The easiest way to do this becomes slow and might bring your computer is to :# create a standstillnew 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 specific family tree.) Contents of this DB_CONFIG file should be: #may want to fiddle with cachesize also #set_cachesize 0 200000000 2 set_lk_max_locks 300000 set_lk_max_objects 300000
Therefore, you should only handle large files by using the GRAMPS GRDB format. You do this by creating a new GRDB 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 Edit{{->Preferences->General menu tab, the importing of data will then be much faster.}}
Also 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) so you only have to use a smaller file.
<br clear="all">
== Default view: bookmarks and active person ==
As there are many people, loading the person view might take some time. See a comparison of [[GRAMPS Performance|performance]] on large datasets, between different GRAMPS versions.
As there are many people, loading the person view might take some time. See a comparison of [[Gramps Performance|performance]] on large datasets, between different 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. Those type of gramplets slow everything down enormously.
== Avoid general filters ==
Filters search all the data looking for the people who satisfy your query. Try to avoid this on large files.
{{man tip|Search letters|Fast search can be done by enabling column search (disable {{man label|Sidebar}} on {{man menu|View}} menu), but this will search all letters on words into the column, not only the first letters.}} For name searches do the followinga 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, click ''use the keyboard shortcut {{man key press|CTRL-|F'' first}}. This will expand all the nodes and allows to search more specifically. == Flat views are faster than Tree views == Using a large database and person treeview needs to often rebuild the view.
== Please contribute ==If you have more tips for working with large databases, please share them hereFlat person view (list) is faster.

Navigation menu