Closed jmehreth closed 6 years ago
Thanks for bringing this to our attention. Could you maybe try to create an additional new project and download an ecoinvent version lower than 3.5 and see how the performance is there? I suspect that the performance decrease is not caused by 3.5 itself, but some change in brightway.
created a new project and downloaded ecoinvent v3.3. the performance is indeed about as bad as with v3.5.
might the biosphere flows play a role, too? (since they differ from the project with good performance and the two projects with bad performance)
How old is the database in your old, fast project?
Raised an issue in bw2data with more detailed tests and an attempt to find the reason for this performance decrease: https://bitbucket.org/cmutel/brightway2-data/issues/60/massive-sqlite-query-performance-decrease
the above project is the one with "normal" performance. the two _modify databases are the ones where I copied/adapted processes, thus the more recent dates under "last modified".
This is now fixed in #191, conda update activity-browser-dev
and your projects will all be fast again. New projects are fixed in brightway, for old slow projects it will take a bit longer to open them the very first time, but after that everything should run the way it used to.
the AB is running extremely slow with ecoinvent 3.5, especially considering browsing the database:
searching for an activity (here: "aluminium"): ~75sec fuzzy search: I quit after 5min of waiting selecting an activity (until it appears on the left): ~9sec
interestingly: calculating runs about as quickly as before; sankey, however, a lot slower sankey (here: 2 activities and 4 LCIA methods): ~30sec
I doubt that the only reason is the increased size of both biosphere (now 4'246 flows) and ecoinvent DBs (now 16'022 units).