15,091
edits
Changes
no edit summary
==Loading the file==
===BSDDB backend==={{man note|Should work for BSDDB versions of Grampsversion 5.1.x and earlier|}}
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
set_lk_max_locks 300000
set_lk_max_objects 300000
===SQLite backend===
Insert following line after the connect statement at line 103 in the [https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/plugins/db/dbapi/sqlite.py ''gramps/plugins/db/dbapi/sqlite.py''] file.
self.__connection.execute("PRAGMA cache_size = -50000")
A positive value sets the size in bytes. A negative value sets the size in pages. The size of a typical page is 4096 bytes.
The default value is -2000 which means 2000 pages of 4096 bytes each.
{{-}}
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 Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|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.
For a surname search:
* click Click on a person in the [[Gramps Gramps_6.0_Wiki_Manual_-_Categories#People_Category|People Grouped 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 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 views are faster than Tree views ==
Using a large family tree database and person treeview the People grouped tree view needs to often rebuild the view. especially after adding or deleting an object eg: Flat person view People (list) view is fasterthan grouped view.
=See also=