I’ve got a nice 32 core intel chip (14th gen) with 64 mb of RAM and lots of usable disk space. I’m using slackware64-current on a new install with a new ~ directory to avoid cruft from my ancient ~ directory. I’ve got 32 GB set aside for tiles. My gimp is the latest pull from git master, as is my darktable. I use darktable to ‘develop’ nef files, which are then imported into gimp.
I’m finding that importing from darktable to gimp results in just one core being used. It can take 30-40 seconds to open an exr file. If I use darktable to export a tif file instead, gimp opens it in seconds.
In the past, gimp has opened exr files very quickly, using available cores, and it still does on one of my machines. I have not rebuilt that machine as I have the one I’m using right now. I would think that with fresh installs of gimp and darktable, both build from git master, and a new ~ directory as well, that my system should be very clean and free of cruft. On my clean machine, I have a problem and on the machine with 10 years of cruft, gimp is as speedy as one would want. I’m pretty sure this is not a DT issue.
It is indeed cruft. I mounted my old home partition, and wowie-zowie gimp opens the DT exr in a blinding flash. Who the h**l knows. I’m a happy camper, but I suspect that there are some sad campers out there.
It’s fixed for me, and I kept my new install. I copied from my old home directory .cache, .config and .local to my new home directory. I’ll be adventurous within a few days, and I’ll try to narrow down the difference between what works with the new, and what I actually need from the old to make gimp import the exr files quickly.