JSONLD export can be very, very long

[lucasguffroy59]

Hello,

So, with my previous DB I had no problem (~15k processes linked to ~78k flows, the raw derby DB folder was 1,37GB), a JSONLD export could take between 5 and 10min. The zip containing my export at the end was ~270MB.

But recently I got an update of this database (now ~17k processes linked to ~150k flows, raw derby DB folder is now 2,16GB, so slightly bigger, but not that much, right ?) and the JSONLD export now takes very, very, very long. I just let my laptop running for the whole night to get my export. The resulting zip containing my export is ~430MB. So, it takes a whole night instead of 10min for ~150MB added to my export size.

I run this on a Macbook pro M1.

Is there something that could explain an exponentially longer time for a slightly bigger database export ?

Have a good day !

[lando84]

Hi all,

I got similar problems during my experiments using OpenLCA and the olca-core/olca-io libraries in Java projects.
Please take in consideration that, on my system I have UBUNTU as operating system, 32Gb RAM and 12th Gen i7 Processor with 12 cores (a fairly powerful PC).

Import and export operations (both JsonLD and Ilcd files) are very slow, both by means of olca-io library and the usage of OpenLCA desktop app. Also the calculation takes a lot of time (both in OpenLCA desktop and by means library). Moreover, I can not install "additional calculation libraries" through the Settings > Configuration page of desktop app.
I also noticed that on my collegue's PC (Macbook Pro i7 16 GB) is faster than me (20 minutes vs 50 seconds).
Do you have some suggestion or tip for solving this performance slow-down?

[francoislerall]

Hello!
Is it better with the newest version of openLCA?
Regards,
François