Thanks for your comments and suggestions, everyone. I was pretty sure Webapp wouldn't be the problem with the right database, but Gramps application performance was a question.  The http://www.gramps-project.org/wiki/index.php?title=GRAMPS_Performance wiki page was great! I hadn't encountered that page before (gramps is well documented!)

I used the db03 dataset on Gramps 3.4. My quad 925 AMD with 8 gig of ram imported the data in 50 minutes 40 seconds. Program performance after the import was satisfactory. This sets my mind at ease regarding Gramps suitability for my project.



On Fri, Oct 12, 2012 at 1:27 AM, Robert Cawley <rjc@cawley.id.au> wrote:
On Thu, 2012-10-11 at 11:23 +0200, Benny Malengier wrote:
>
>
> 2012/10/11 Dave Burkholder <thinkwelldesigns@gmail.com>
>         Hello everyone. I'm Dave and I've been lurking this list for
>         some time, considering migrating a project from another
>         genealogy program to Gramps.  The project already has 140,000+
>         names.
>
>         For the most part, I hope to be using Webapp on a Postgresql
>         database (and I would like to contribute to the Webapp in
>         time) but I'll want to be using Gramps application also, if
>         possible. Is that out of the question for so many names?
>
> Some things will be really slow I expect.
> Biggest problem is probably the import of so many names. Import
> happens as one database commit, but on importing so many names, you
> will go over the database page limit of one commit.
> That is a setting you can change however somewhere in the code. See
> http://gramps-project.org/wiki/index.php?title=Known_issues#GRAMPS_runs_out_of_locks
> Improving the import code to have it more performant for such a case
> would be a great addition :-)
>
> Once imported, I'm not sure the views will work good or not. We
> reworked the views to have them performant, but if that actually works
> on 140.000 is unknown. I'd be interested to know though.

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).

Avoid leaving gramplets which do a lot a database work active - deep
connections seems to be the worst case - as these slow everything down
enormously.

I do have the show relationship to home person enabled though and this
does not seem to slow things appreciably.

Inital import of the database from either gramps format or gedcom is
tiresome though and can take a few hours. (would be really good if
import could be sped up.) As stated above you will need to adjust the
number of allowable locks. I current use:
max_locks 300000 and
max_objects 300000
I used to get away with half this, but not any more.
The easiest way to do this is to create an empty database the add a file
DB_CONFIG to the database directory before importing.
Contents of DB_CONFIG

#may want to fiddle with cachesize also
#set_cachesize 0 200000000 2
set_lk_max_locks 300000
set_lk_max_objects 300000

Robert


>
> Latest results are here:
> http://www.gramps-project.org/wiki/index.php?title=GRAMPS_Performance
> You see that last test was with 3.3.0. on 120000+ people. Starting
> gramps up on the person listview was 15 sec. Switching to event view
> 1s (normally more events than you have people). Sorting event on date
> however was 30 sec, as obviously the entire table of dates must be
> sorted in memory.
> I suppose people would expect sorting to be slow in this case.
>
> Benny
>
>
>
>         What's the largest project Gramps has ever handled, at any
>         version?
>
>
>                 On Mon, Oct 1, 2012 at 3:20 AM, Jérôme
>                 <romjerome@yahoo.fr> wrote:
>                         >  For a Surname it takes around 20 seconds
>                         until the
>                         > result is displayed. I've nearly 28000
>                         persons in my database.
>
>
>                         "Flat views are faster than Tree views"
>
>                         http://www.gramps-project.org/wiki/index.php?title=Tips_for_large_databases
>
>                         Try to rather to "display Surnames" via person
>                         list view!
>                         Surnames will not be grouped (parent node),
>                         but I know that it will be
>                         faster.
>
>                         Note, I got this problem with Place Tree View
>                         in the past (around 38 000
>                         rows/entries) and I did not test
>                         Citations/Sources Tree View yet, which
>                         seems to use an other method (iteration,
>                         cursor) for displaying such
>                         grouped data.
>
>
>                         Jérôme
>
>                         Le 30/09/2012 15:53, Anton Huber a écrit :
>                         > Hello,
>                         >
>                         > searching in the database using person view
>                         is very slow on all my personal
>                         > computers and notebooks. For a Surname it
>                         takes around 20 seconds until the
>                         > result is displayed. I've nearly 28000
>                         persons in my database. Is there a
>                         > way to make searching more comfortable for
>                         big database?
>                         >
>                         > Best regards,
>                         >
>                         > Anton
>                         >
>                         >
>                         >
>
>                         >
>                         ------------------------------------------------------------------------------
>                         > Everyone hates slow websites. So do we.
>                         > Make your web apps faster with AppDynamics
>                         > Download AppDynamics Lite for free today:
>                         >
>                         http://ad.doubleclick.net/clk;258768047;13503038;j?
>                         >
>                         http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>                         >
>                         >
>                         >
>                         >
>                         _______________________________________________
>                         > Gramps-devel mailing list
>                         > Gramps-devel@lists.sourceforge.net
>                         >
>                         https://lists.sourceforge.net/lists/listinfo/gramps-devel
>                         >
>
>
>
>                         ------------------------------------------------------------------------------
>                         Got visibility?
>                         Most devs has no idea what their production
>                         app looks like.
>                         Find out how fast your code is with
>                         AppDynamics Lite.
>                         http://ad.doubleclick.net/clk;262219671;13503038;y?
>                         http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>                         _______________________________________________
>                         Gramps-devel mailing list
>                         Gramps-devel@lists.sourceforge.net
>                         https://lists.sourceforge.net/lists/listinfo/gramps-devel
>
>
>
>
>
>
>         ------------------------------------------------------------------------------
>         Don't let slow site performance ruin your business. Deploy New
>         Relic APM
>         Deploy New Relic app performance management and know exactly
>         what is happening inside your Ruby, Python, PHP, Java,
>         and .NET app
>         Try New Relic at no cost today and get our sweet Data Nerd
>         shirt too!
>         http://p.sf.net/sfu/newrelic-dev2dev
>         _______________________________________________
>         Gramps-devel mailing list
>         Gramps-devel@lists.sourceforge.net
>         https://lists.sourceforge.net/lists/listinfo/gramps-devel
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________ Gramps-devel mailing list Gramps-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gramps-devel

--
Robert Cawley
Ph: +61 2 9543 1241
rjc@cawley.id.au
rjc047@westnet.com.au
rjc047@optusnet.com.au




------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Gramps-devel mailing list
Gramps-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gramps-devel