Difference between revisions of "Talk:Gramps 3.0 Wiki Manual - Manage Family Trees"

From Gramps
Jump to: navigation, search
Line 11: Line 11:
  
 
:I think the original comment refers to large files/databases. If you are loading a huge xml or gedcom file into memory then it can fill the whole physical memory leading to swapping. A database will scale better with large data volumes. --[[User:Gburto01|Gburto01]] 05:41, 11 September 2007 (EDT)
 
:I think the original comment refers to large files/databases. If you are loading a huge xml or gedcom file into memory then it can fill the whole physical memory leading to swapping. A database will scale better with large data volumes. --[[User:Gburto01|Gburto01]] 05:41, 11 September 2007 (EDT)
 +
 +
:The statement in the manual tries to link the speed of the access with whether or not it is in memory. Whether it is faster or not will be a function of indices, in memory/not, and size of database. If the statement is still true (can you load a GEDCOM file without a database?) then it should be changed to something like: "XML and GEDCOM databases are loaded into memory without the use of indices. For large family trees, this can cause two problems: you may run out of memory, and it may take some time to perform certain operations. Thus, it is often better to create an empty grdb database and then import the XML and GEDCOM file into it." --[[User:Dsblank|Dsblank]] 07:27, 12 September 2007 (EDT)
  
  

Revision as of 11:27, 12 September 2007

"""
Opening databases

XML and GEDCOM databases require all data to be held in memory. GRAMPS' native grdb format does not. Thus, a database with a grdb 
format can access data quicker and more efficiently.
"""

More quickly access the disk than memory? I don't think so. But maybe this option goes away with the new Family Tree Manager anyway? --Dsblank 07:21, 10 September 2007 (EDT)

The reason this is faster is due to the fact that a database has indexes, and the other format do not. bmcage 03:52, 11 September 2007 (EDT)
I think the original comment refers to large files/databases. If you are loading a huge xml or gedcom file into memory then it can fill the whole physical memory leading to swapping. A database will scale better with large data volumes. --Gburto01 05:41, 11 September 2007 (EDT)
The statement in the manual tries to link the speed of the access with whether or not it is in memory. Whether it is faster or not will be a function of indices, in memory/not, and size of database. If the statement is still true (can you load a GEDCOM file without a database?) then it should be changed to something like: "XML and GEDCOM databases are loaded into memory without the use of indices. For large family trees, this can cause two problems: you may run out of memory, and it may take some time to perform certain operations. Thus, it is often better to create an empty grdb database and then import the XML and GEDCOM file into it." --Dsblank 07:27, 12 September 2007 (EDT)



If a family tree contains archives (snapshots of previous version), you will be able to open them too by the same procedure.


This is not what Database_Formats#The_Future_-_GRAMPS_3.0 says. And as my current GRAMPS 3.0 won't display the Archive button, I can't try it out. Has the design changed? --Annej 07:15, 11 September 2007 (EDT)

To see the archive button you must have RCS installed. I just quickly added extra sections in the page so as not to forget that this must be added from memory. Database_Formats#The_Future_-_GRAMPS_3.0 is more correct, I did not notice I could copy paste. I see you updated the page in the meantime, good work! bmcage 10:26, 11 September 2007 (EDT)