Difference between revisions of "Tips for large databases"

From Gramps
Jump to: navigation, search
(Avoid Gramplets)
m
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{out of date|check accuracy}}
+
{{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!! https://www.reddit.com/r/gramps/comments/dzevcl/database_size_limit_for_gramps/fb6hdbj/ " -->
  
Large data files, what to do, and what not to do.
+
Large family tree data files, what to do, and what not to do.
  
 
==Loading the file==
 
==Loading the file==
 
+
{{man note|Should work for BSDDB versions of Gramps}}
Initial import of a large (100,000+) database from either Gramps XML formats or GEDCOM is can take a few hours. You will need to adjust the
+
Initial import of a large (100,000+) database from either Gramps XML formats or GEDCOM can take a few hours. You will need to adjust the number of allowable locks. For 140,000 people you should use:  
number of allowable locks. For 140,000 people you should use:  
 
 
* ''max_locks'' 300000
 
* ''max_locks'' 300000
 
* ''max_objects'' 300000
 
* ''max_objects'' 300000
Line 13: Line 13:
 
# create a new Family Tree
 
# create a new Family Tree
 
# exit Gramps
 
# exit Gramps
# add a '''DB_CONFIG''' file to the database directory before importing (see '''gramps -l''' output for the directory of a specific family tree.)
+
# 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:
 
Contents of this DB_CONFIG file should be:
Line 27: Line 27:
 
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 [[Relationships screenshot|relationships view]] before opening the family tree. This will open the active person and their family extremely fast, independent of the amount of data you gathered.
+
You can circumvent this load time by going to the [[Gramps Relationships Category view screenshot|relationships view]] before opening the family 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.
 
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 ==
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 gramplets which do a lot of database work. The '''[[Addon:Deep_Connections_Gramplet|Deep Connections]]''' Gramplet seems to be the worst case. Those type of gramplets slow everything down enormously.
  
 
== Avoid general filters ==
 
== Avoid general filters ==
Line 41: Line 45:
  
 
For a surname search:
 
For a surname search:
* click  on a person in the [[People screenshot|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.
+
* click  on a person in the [[Gramps People Category 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.
 
* 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.
  
Line 49: Line 53:
  
 
Flat person view (list) is faster.
 
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}}.
 
 
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]

Latest revision as of 02:43, 5 January 2022

Tango-Dialog-information.png
The advice on this page was for older versions of Gramps so may not work for you. Please update as needed.

Gramps-notes.png

This article's content is incomplete or a placeholder stub.
Please update or expand this section.


Large family tree data files, what to do, and what not to do.

Loading the file

Gramps-notes.png
Should work for BSDDB versions of Gramps

Initial import of a large (100,000+) database from either Gramps XML formats or GEDCOM can take a few hours. You will need to adjust the number of allowable locks. For 140,000 people you should use:

  • max_locks 300000
  • max_objects 300000

The easiest way to do this is to:

  1. create a new Family Tree
  2. exit Gramps
  3. 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:

#may want to fiddle with cachesize also
#set_cachesize 0 200000000 2
set_lk_max_locks 300000
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 performance on large datasets, between different Gramps versions.

You can circumvent this load time by going to the relationships view before opening the family 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 Edit > Preferences Display tab change the Status bar option from Relationship to the home person to Active person's name and ID.

Avoid Gramplets

Avoid gramplets which do a lot of database work. The 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.

Tango-Dialog-information.png
Search letters

Fast search can be done by enabling column search (disable Sidebar on View menu), but this will search all letters on words into the column, not only the first letters.


For a surname search:

  • click on a person in the 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 CTRL+F. 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.

Flat person view (list) is faster.