From: Kees B. <kee...@xs...> - 2006-09-26 19:04:40
|
Op dinsdag 26 september 2006 20:17, schreef Kees Bakker: > Hi, > > For people like me - just playing with gramps and using a GEDCOM output > from another program - it is annoying that it takes a long time to read > in a GEDCOM file. I did it in the past with the 2.0.x version and I > remember it was much faster (after fixing the progress bar updates). > I have a large GEDCOM file and it takes more than 20 minutes to import > it (in an empty database!). > > CPU usage is only 25%, so I guess it is very busy with file IO (database > updates?). > > Does anyone have a suggestion what I can do to speed it up? This looks suspicious. _GrampsDbBase.py: def transaction_begin(self, msg="", batch=False, match=False, no_magic=False): _ReadGedcom.py: self.trans = self.db.transaction_begin("",not use_trans,no_magic) The 'match' parameter of transaction_begin() is not taken into account. But I have no idea what this 'use_trans' supposed to mean. Oh, and Don seems to be needing a wider screen. Why do I say this? Look at the changes of _GrampsDbBase.py in revision 6290. He made changes such as this: def transaction_begin(self, msg="", batch=False, match=False, no_magic=False): into this: def transaction_begin(self, msg="", batch=False, match=False, no_magic=False): Why on earth wrap a line at column 65? - Kees |