From: Benny M. <ben...@gm...> - 2008-11-17 09:03:00
|
For python 2.6 we have removed async write of log as it creates a DbError now. See http://www.gramps-project.org/bugs/view.php?id=2483 The workaround would appear to be close of environment, and create new environment with async set up. This looks like a difficult project to me: at the end of batch the env has to be closed again and opened again, it must be certain no other handles are open at the moment or reference this env, so the global env must be replaced, testing .... Async write was added in the past to increase performance on batch operations, my suggestion would be to see if this still is in issue in python 2.6 with new bsddb, so if people in 2.6 see much slower import of GEDCOM/XML, check and repair, ..., this would be a likely place to gain some performance back. If somebody has a different idea? Benny |