|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
|
|
Extremly slow XML import.Yesterday, when I helped Benny with some sort tests in Windows, I found that doing XML import there
was VERY slow under certain circumstances: Fast XML import about 3 min with 6020 people. GRAMPS: 3.2.0-0.SVN13520M Python: 2.5.1 (r251:54863, Apr 18 2007, 08:51:08... BSDDB: 4.4.5.2 LANG: sv_SE:utf-8 OS: win32 Slow XML import > 50 minutes with same XML. GRAMPS: 3.2.0-0.SVN13520M Python: 2.6.2 (r262:71605, Apr 14 2009, 22:40:02... BSDDB: 4.7.3 LANG: sv_SE:utf-8 OS: win32 I also tried with Gramps 3.1.3 and identical result. It's obviously a difference between Python 2.5.1 and 2.6.2, but what? /Peter ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Gramps-devel mailing list Gramps-devel@... https://lists.sourceforge.net/lists/listinfo/gramps-devel |
|
|
|
Re: Extremly slow XML import.2009/11/7 Peter Landgren <peter.talken@...>:
> Yesterday, when I helped Benny with some sort tests in Windows, I found that doing XML import there > was VERY slow under certain circumstances: > > Fast XML import about 3 min with 6020 people. > GRAMPS: 3.2.0-0.SVN13520M > Python: 2.5.1 (r251:54863, Apr 18 2007, 08:51:08... > BSDDB: 4.4.5.2 > LANG: sv_SE:utf-8 > OS: win32 > > Slow XML import > 50 minutes with same XML. > GRAMPS: 3.2.0-0.SVN13520M > Python: 2.6.2 (r262:71605, Apr 14 2009, 22:40:02... > BSDDB: 4.7.3 > LANG: sv_SE:utf-8 > OS: win32 > > I also tried with Gramps 3.1.3 and identical result. > > It's obviously a difference between Python 2.5.1 and 2.6.2, but what? Interesting. I would rather think bsddb in combination with it might be to blame. But on linux it is always fast? I have 2.5 python here, seems ok to me on linux. Perhaps ask the windows people to profile the import to see where the time goes to. So do import Utils and where the import function is called as import_function, rename it to _import_function, and create a new import_function that has: def import_function(): Utils.profile(_import_function) Benny > > /Peter > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Gramps-devel mailing list > Gramps-devel@... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Gramps-devel mailing list Gramps-devel@... https://lists.sourceforge.net/lists/listinfo/gramps-devel |
|
|
|
|
| dbshelve.py:256(put) |
Stephen, can you forward this research to the windows list.
So, dbshelve.py is 93 times faster in linux than windows. This means windows users have really bad performance on all batch operations (import, change tools, ....), just look at the output. For peter, an import of 3 min in linux is more than 50 min in windows.
My guess is that or the filesystem is to blame (windows ntfs is not as good as what is present on linux) but cannot be for so much? Otherwise contact the bsddb pybsddb people to know if there is something windows users can do to have bsddb working at normal speed.
Perhaps time this yourself once too.
Benny2009/11/8 Peter Landgren <peter.talken@...>
Yes,
the last hint made it.
I have run in both my Windows box (1.7 GHz 512 MB) and my Linux box (2.4 GHz 1 GB)
and compared the result:
This call:
takes the longest time in both systems.
dbshelve.py:256(put)
If I compare the "tottime" the Linux system is about 5 times faster than the windows except
for the dbshelve.py:256(put) which is 93 times faster in the Linux box. I have attached the outputs from the profiling and the comparison.
I have no deeper knowledge how to interpret the profiling.
/Peter
| Free embeddable forum powered by Nabble | Forum Help |