I installed darktable 1.4.2 instead of the git version, and the performance is much better. The output of -d perf doesn't say whether demosaic runs on the GPU or CPU with 1.4.2, but it says 0.095 secs (0.080 CPU) instead of 0.737 secs (3.467 CPU) that I got with the git version. This is evident when using darktable, with 1.4.2 the image shows immediately when switching to the darkroom, with the git version it takes a couple of seconds before the image appears.
I tried moving ~/.config/darktable to make sure it wasn't my settings that caused the issue, but it made no difference. I also installed latest git, same issue. /Per On 2014-10-08 01:00, Per Östlund wrote: > Hi, > > I've felt that darktable has been rather slow for a while now, and > when trying to figure out why I found out that even though I have > OpenCL activated it's running demosaicing on the CPU. Running > darktable with -d perf and opening an image gives this: > > [dev_pixelpipe] took 0.000 secs (0.000 CPU) initing base buffer [full] > [dev_pixelpipe] took 0.015 secs (0.013 CPU) processed `let's go > float!' on GPU, blended on GPU [full] > [dev_pixelpipe] took 0.006 secs (-0.000 CPU) processed `white balance' > on GPU, blended on GPU [full] > [dev_pixelpipe] took 0.006 secs (0.003 CPU) processed `highlight > reconstruction' on GPU, blended on GPU [full] > [dev_pixelpipe] took 0.737 secs (3.467 CPU) processed `demosaic' on > CPU, blended on CPU [full] > [dev_pixelpipe] took 0.006 secs (0.007 CPU) processed `base curve ' on > GPU, blended on GPU [full] > [dev_pixelpipe] took 0.003 secs (0.000 CPU) processed `input color > profile' on GPU, blended on GPU [full] > [dev_pixelpipe] took 0.002 secs (0.003 CPU) processed `levels' on GPU, > blended on GPU [full] > [dev_pixelpipe] took 0.004 secs (0.000 CPU) processed `sharpen ' on > GPU, blended on GPU [full] > [dev_pixelpipe] took 0.004 secs (0.000 CPU) processed `output color > profile ' on GPU, blended on GPU [full] > [dev_pixelpipe] took 0.091 secs (0.007 CPU) processed `gamma' on CPU, > blended on CPU [full] > [dev_process_image] pixel pipeline processing took 0.874 secs (3.500 CPU) > > For some reason it's running everything on the GPU, except for > demosaic and gamma which seem to take most of the time. I haven't > touched the demosaic module (or any other module) in this case, so > it's using the default PPG which I thought could use OpenCL. Or am I > mistaken? > > -d opencl doesn't show any kind of errors, and even says that it's in > fact loading several PPG kernels when starting darktable. This is with > darktable built from git a couple of days ago, on ArchLinux x86_64. > The GPU is a GeForce GTX 560 Ti using Nvidia 340.32 drivers. Deleting > ~/.cache/darktable made no difference. > > Cheers, > Per Östlund ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
