Thanks. That's a small advantage for opencl_use_pinned_memory=TRUE.
Still even with the flag set to TRUE we loose quite some time in the
host_memory->device_memory step. I expect that I can change our code to
get some further improvements there in the next days.
Ulrich
Am 15.09.2016 um 16:10 schrieb Chester:
ULrich: here are my config and the two files:
darktable --version
this is darktable 2.0.6
copyright (c) 2009-2016 johannes hanika
darktable-...@lists.darktable.org
compile options:
bit depth is 64 bit
normal build
OpenMP support enabled
OpenCL support enabled
Lua support enabled, API version 3.0.0
Colord support enabled
gPhoto2 support enabled
GraphicsMagick support enabled
inxi
CPU~Quad core Intel Core i7 930 (-HT-MCP-) speed/max~1600/2801 MHz
Kernel~4.4.0-36-generic x86_64 Up~1:50 Mem~2072.5/20069.5MB
HDD~3768.8GB(3.6% used) Procs~268 Client~Shell inxi~2.2.35
inxi -G
Graphics: Card: NVIDIA GF106 [GeForce GTS 450]
Display Server: X.Org 1.18.3 drivers: nvidia (unloaded:
fbdev,vesa,nouveau)
Resolution: 1680x1050@59.88hz, 1920x1200@59.95hz
GLX Renderer: GeForce GTS 450/PCIe/SSE2
GLX Version: 4.5.0 NVIDIA 361.42
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
