Re: [Gramps-users] large db performance and caching

[Enno B. <enn...@gm...>]

Tim,
> I did seven tests with various cenarios:
>
> The first test involved importing a gedcom that was 7megs with
> 15,000individs
>    - tested with gramps default settings
>    - then I test with the dbcont,py replacement file (supplied by enno) --
> there was only a 2 second gain out of 7.5 minutes
>    - replaced gramps default dbcont file and placed a DB_CONFIG file in the
> test db folder - again no different time in import speed.
Funny is that I do think that I saw a difference. Remember that the 
cache is set on creation, so if you put the patched file in place, you 
need to create a new database after that to put the larger cache into 
effect. You also need to make sure that the replacement file is actually 
used.

In my setup., I normally use a Gramps version that I install myself, 
which I access from the menu. For tests, I build Gramps inside 
~/gramps-source, then run that with python src/gramps.py, so that I'm 
absolutely sure that I run the test version.
> Just a note: a few days ago when I imported into a db that was in a ramdisk,
> had the greatest speed improvements... but I couldn't create a big enough
> ram disk to import a large gedcom file (and using a ramdisk and transferring
> the file may have cause corruption in the db -- so be warned)
This sort of suggests that a large disk cache, one that actually delays 
writes to the HD, may have a large effect, but to my regret I have no 
idea how to create such a thing.

regards,

Enno