In terms of numbers this fits. The tiling code splits this image processing step as the full image would be too big. The tile to be processed is 5172 x 3666 pixels in size. This requires an image buffer of 289MB. We need four full buffers (in, out, tmp, U2) and we need additional four small buffers each with a fourth of the full size (one color channel instead of four):
total memory = 289MB * (4 + 4 * 1/4) = 1446MB Add the 600MB headroom and you end up at about 2GB GPU memory. I don't understand why we have issues here. Ulrich Am 20.10.2014 um 18:23 schrieb Matthias Bodenbinder: > Am 20.10.2014 um 07:39 schrieb Ulrich Pegelow: >> What denoising method did you chose in that module? Non-local means or >> wavelet? >> >> Best wishes >> >> Ulrich >> > I am always using non-local means. I have attached an example dtstyle file. > > Here the output of "darktable -d opencl -d perf" when it happens with > opencl_memory_headroom: 600 > ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
