# Performance problems with large datasets **URL:** \ **Category:** Development\ **Created:** [March 27, 2026, 10:27pm UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271 "2026-03-27T22:27:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![bhofmann](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/bhofmann/32/8446_2.png) [@bhofmann](https://gramps.discourse.group/u/bhofmann)\ **Post date:** [March 27, 2026, 10:27pm UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271/1 "2026-03-27T22:27:39Z")
I’m new to Gramps and recently imported my wife’s GEDCOM data. She has about 186,000 names and the system is very sluggish and takes 40-90 seconds for a simple name search. With my own development projects I would look at the database and start making indexes, materialized views, and other creative ways to improve performance. I know this tree is larger than most but from a development perspective, it isn’t a huge dataset. I searched through this forum and didn’t see any recent discussions about performance. Is that something you’re working on? Is there anything already in the roadmap? I’m fine getting set up and helping with development but I didn’t want to start something that’s already in progress. Thanks! Ben ---
**Author:** ![dsblank](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/dsblank/32/3649_2.png) [@dsblank](https://gramps.discourse.group/u/dsblank)\ **Post date:** [March 27, 2026, 11:10pm UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271/2 "2026-03-27T23:10:49Z")
Hey, Ben; we do have some things on the roadmap! Can you say exactly which search you were using? What screen? There are a few things we’re working on, and more that we could. ---
**Author:** ![bhofmann](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/bhofmann/32/8446_2.png) [@bhofmann](https://gramps.discourse.group/u/bhofmann)\ **Post date:** [March 27, 2026, 11:38pm UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271/3 "2026-03-27T23:38:45Z")
Thanks for the quick response. I was using the People Filter. I attached an image to show it. ![Gramps_search](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/9/9b692294d640cf7e4da579e72f1b899495fff869.png) ---
**Author:** ![romjerome](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/romjerome/32/1489_2.png) [@romjerome](https://gramps.discourse.group/u/romjerome)\ **Post date:** [March 28, 2026, 5:45am UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271/4 "2026-03-28T05:45:17Z")
Making such search on names from `People View` instead of the `Grouped People View` (see toolbar, category navigator or the menu) might provide better performances. There is also a dedicated wiki page for tips with large databases. This will not be a solution, but this could help to understand current limits (some of them might be outdated on recent configs too). e.g., 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 Grouped Category view](https://gramps-project.org/wiki/index.php/Gramps_6.0_Wiki_Manual_-_Categories#People_Category). 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 family tree database and the People grouped tree view needs to often rebuild the view especially after adding or deleting an object eg: Flat People (list) view is faster than grouped view. [https://gramps-project.org/wiki/index.php?title=Tips\_for\_large\_databases](https://gramps-project.org/wiki/index.php?title=Tips_for_large_databases) ---
**Author:** ![dsblank](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/dsblank/32/3649_2.png) [@dsblank](https://gramps.discourse.group/u/dsblank)\ **Post date:** [March 28, 2026, 1:17pm UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271/5 "2026-03-28T13:17:05Z")
@bhofmann Thanks for sharing your data! @romjerome is correct that using a flat view is faster, but not significantly. There are two significant factors: 1. A bug hidden in some innocuous-looking code that is now fixed. That alone reduces your 77 seconds to probably around 10 seconds. 2. Being able to use SQL. With a solution planned for Gramps 6.1, that reduces the time to 0.41 seconds (my test database has 100k people). ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/4/4ed2278748ca3b5568a9f8fbce5b5c0c087bc52e.png) CC: @UlrichDemlehner ---
**Author:** ![bhofmann](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/bhofmann/32/8446_2.png) [@bhofmann](https://gramps.discourse.group/u/bhofmann)\ **Post date:** [March 28, 2026, 5:35pm UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271/6 "2026-03-28T17:35:56Z")
Thank you both! I figured you’d be on top of it. I’ll try the flat view as I wait for Gramps 6.1 to be released. Thanks! ---
**Author:** ![bhofmann](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/bhofmann/32/8446_2.png) [@bhofmann](https://gramps.discourse.group/u/bhofmann)\ **Post date:** [March 28, 2026, 5:36pm UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271/7 "2026-03-28T17:36:53Z")
Thank you! I’ll check it out. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\ **Post date:** [April 27, 2026, 5:37pm UTC](https://gramps.discourse.group/t/performance-problems-with-large-datasets/9271/8 "2026-04-27T17:37:35Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.