Gramps Performance - Revision history

Patsyblefebre: Gramps

2013-01-21T22:48:13Z

Gramps

Patsyblefebre: Patsyblefebre moved page GRAMPS Performance to Gramps Performance: Gramps

2013-01-21T22:47:07Z

Patsyblefebre moved page GRAMPS Performance to Gramps Performance: Gramps

Bmcage: /* User Stories */

2012-10-12T07:51:38Z

‎User Stories

Bmcage at 07:51, 12 October 2012

2012-10-12T07:51:07Z

Romjerome: /* Genealogical datasets */

2011-09-09T20:45:16Z

‎Genealogical datasets

Romjerome: /* Dataset summaries */

2011-09-09T20:37:16Z

‎Dataset summaries

Romjerome: /* Genealogical datasets */

2011-09-09T20:32:16Z

‎Genealogical datasets

Romjerome: /* Genealogical datasets */

2011-09-09T07:58:31Z

‎Genealogical datasets

Romjerome: /* Genealogical datasets */

2011-09-09T07:56:49Z

‎Genealogical datasets

Romjerome: /* Performance results */

2011-09-08T15:45:31Z

‎Performance results

@@ Line 1: / Line 1: @@
-Comparison of performance on large datasets between different GRAMPS versions
+Comparison of performance on large datasets between different Gramps versions
 ==Performance tests==
-It is important that GRAMPS performs well on datasets in the 10k to 30k range. A good benchmark is to test GRAMPS on a 100k range dataset, and keep track of performance with every new version.
+It is important that Gramps performs well on datasets in the 10k to 30k range. A good benchmark is to test Gramps on a 100k range dataset, and keep track of performance with every new version.
-Furthermore, this page can serve as proof to users that the present version of GRAMPS is '''not slow'''. From version 2.2.5 onwards, special attention will be given to performance, so that it does not deteriorate due to changes.
+Furthermore, this page can serve as proof to users that the present version of Gramps is '''not slow'''. From version 2.2.5 onwards, special attention will be given to performance, so that it does not deteriorate due to changes.
 If you want to work with a large database, read [[Tips for large databases]].
@@ Line 30: / Line 30: @@
 ==General setup==
-Comparison should be with equal hardware, and on the same datasets to be fair. Optimal representation may be chosen, so for GRAMPS, tests are done in the native database format, called GRAMPS GRDB format.
+Comparison should be with equal hardware, and on the same datasets to be fair. Optimal representation may be chosen, so for Gramps, tests are done in the native database format, called GRAMPS GRDB format.
 Should somebody want to publish results of commercial software under windows, this is allowed, but should be fair: same hardware and dataset, so test on a dual-boot machine, and use the internal format of the program.
@@ Line 50: / Line 50: @@
 '''FAQ'''
-* ''My computer hangs on open, eating memory?'' These are LARGE datasets, so do NOT open them directly. For GRAMPS open them as follows: create a new Family Tree. Open it and go to the import menu and import the dataset.
+* ''My computer hangs on open, eating memory?'' These are LARGE datasets, so do NOT open them directly. For Gramps open them as follows: create a new Family Tree. Open it and go to the import menu and import the dataset.
 * ''What is tar.bz?'' This is a compression format. You must uncompress the file before importing it
-* ''Can you provide the GEDCOM?'' No. Offering GEDCOM has the danger of attracting to much traffic to this site. If you need GEDCOM, you should install GRAMPS, import the dataset, and then choose "Export to GEDCOM".
+* ''Can you provide the GEDCOM?'' No. Offering GEDCOM has the danger of attracting to much traffic to this site. If you need GEDCOM, you should install Gramps, import the dataset, and then choose "Export to GEDCOM".
 * ''What is in these files?'' See summary at the bottom of this page.
@@ Line 163: / Line 163: @@
 |}
-(*) clean start means computer restart (so also python methods/modules must be loaded and started). Non clean means you have opened GRAMPS with .grdb file before, and open it again. Parts will be still in memory and access will be faster, as well as python being in memory.
+(*) clean start means computer restart (so also python methods/modules must be loaded and started). Non clean means you have opened Gramps with .grdb file before, and open it again. Parts will be still in memory and access will be faster, as well as python being in memory.
 === Performance results ===
-General remark: tests are done with in GRAMPS preferences: '''transactions enabled''', unless indicated otherwise with '''notrans'''. This gives a performance boost. ''For safety: only change this setting on an empty database -- you are warned!''
+General remark: tests are done with in Gramps preferences: '''transactions enabled''', unless indicated otherwise with '''notrans'''. This gives a performance boost. ''For safety: only change this setting on an empty database -- you are warned!''
 {| {{prettytable}}
 |-
-!Comp !! GRAMPS !! data !! T01 !! T02
+!Comp !! Gramps !! data !! T01 !! T02
 |-
 |H03 ||bgcolor="#ffa0a0"| 2.2.4 notrans || d01 (xml)||bgcolor="#ffa0a0"| 2h || 542.6MB (v11)
@@ Line 203: / Line 203: @@
 {| {{prettytable}}
 |-
-!Comp !! data !! GRAMPS !! T03 !! T04 !! T05 !! T06 !! T07 !! T08 !! result
+!Comp !! data !! Gramps !! T03 !! T04 !! T05 !! T06 !! T07 !! T08 !! result
 |-
 |H02 || d01 ||bgcolor="#ffa0a0"| 2.2.4 || T03 = 4m17s || T04 = ? || T05 = ?/? || T06 = ? || T07 = ? || T08 = ||bgcolor="#ffa0a0"|
@@ Line 292: / Line 292: @@
 One can fine tune some things to obtain better results. An overview.
-See if GRAMPS can pass this:
+See if Gramps can pass this:
 * [http://www.tamurajones.net/TheConfuciusChallenge.xhtml The Confucius Challenge]
 ** [http://www.tamurajones.net/ConfuciusCascade.xhtml Confucius Cascade] a real-world test based on consisting of increasingly gigantic GEDCOMs, tough time limits.

@@ Line 11: / Line 11: @@
 == User Stories ==
 Running the tests can be slow, so here some user testimonies about Gramps Performance
-=== Robert 2012-10 ===
+=== Robert 2012-10, version  3.3.1 ===
 I work with a database of 141,000+names currently without difficulty
 (Gramps 3.3.1-1 on Fedora 16).

← Older revision		Revision as of 07:51, 12 October 2012
Line 8:		Line 8:

	If you want to work with a large database, read [[Tips for large databases]].		If you want to work with a large database, read [[Tips for large databases]].
		+
		+	== User Stories ==
		+	Running the tests can be slow, so here some user testimonies about Gramps Performance
		+	=== Robert 2012-10 ===
		+	I work with a database of 141,000+names currently without difficulty
		+	(Gramps 3.3.1-1 on Fedora 16).
		+	Initial start is fairly slow though.
		+	First time to load each view is slow, but subsequent visits to views is
		+	almost immediate.
		+	Initial view load times:
		+	* people 11 to 12 secs
		+	* relationship abt 7 secs
		+	* family 3 to 4 secs
		+	* events 7 to 8 secs
		+	* places 3 to 4 secs
		+	* notes 11 to 12 secs
		+	* ancestry view abt 1 sec or less
		+	* Media abt 2 secs (although I only have about 1000 media in database)
		+	* Repositories almost immediate
		+	* sources about 1 sec - (time selecting a source varies according to number references for that source - my worst case is a civil registry which has about twice as many references as people in my database).

	==General setup==		==General setup==

@@ Line 83: / Line 83: @@
 |[http://www.gramps-project.org/files/stresstestdata/places.gramps places.gramps]
 | 2.5MB
-| 2132
+| 65598 place objects
 |15.3MB
-|Testing only, no sharing, no publication (65598 place objects)
+|Testing only, no sharing, no publication
 |-
 |}

@@ Line 257: / Line 257: @@
   Number of families: 24604
   Unique surnames: 5822
 == Possible Future Optimizations ==

@@ Line 79: / Line 79: @@
 | 13.6MB
 |Private
 |}

@@ Line 68: / Line 68: @@
 |d03_alternate
 |[http://www.gramps-project.org/files/stresstestdata/test_2011-09-07.gramps.tar.bz2 test_2011-09-07.gramps]
-| 11.7MB
+| 11.9MB
 | 124032
 |88.4MB

@@ Line 165: / Line 165: @@
 |H07 ||bgcolor="#a0a0a0"| 3.1.90 - 2009-7-20 (trans?)|| d03 (xml)||bgcolor="#a0a0a0"| 2h:44min  || 2GB *
 |-
-|H08 ||bgcolor="#ffa0a0"| 3.3.0 (+ DB upgrade ...)|| d03 (xml)||bgcolor="#ffa0a0"| 1h:47min || 547MB (v15)
+|H08 ||bgcolor="#ffa0a0"| 3.3.0 (+ DB upgrade v13 ? + v14 + v15)|| d03 (xml)||bgcolor="#ffa0a0"| 1h:47min || 547MB (v15)
 |-
 |H08 ||bgcolor="#ffa0a0"| 3.3.0 || d03_alternate (xml)||bgcolor="#ffa0a0"| 1h:46min!|| 543MB (v15)