Re: [darktable-dev] OpenCL scheduling profiles

2017-04-30 Thread Ulrich Pegelow
Am 30.04.2017 um 19:43 schrieb Christian Kanzian: A bit late, but today I had some time for deeper testing this. In general detection seems to work well and the profile very fast GPU with a single GPU works nice as well. On startup profile was set to multiple GPU, so detection works. Unfortunat

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-30 Thread Christian Kanzian
Hi, > I am interested in your experience, both in terms of automatic detection > of the best suited profile and in terms of overall performance. Please > note that this is all about system latency and perceived system > responsiveness in the darkroom view. Calling darktable with '-d perf' > will o

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Matthias Andree
Am 09.04.2017 um 18:38 schrieb Ulrich Pegelow: > Am 09.04.2017 um 17:29 schrieb Matthias Andree: >>> What's your number of background threads (fourth entry in core >>> options)? >> >> It's currently set to 2, and if removed from the configuration file with >> darktable stopped, >> will revert to 2

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Ulrich Pegelow
Am 09.04.2017 um 17:29 schrieb Matthias Andree: What's your number of background threads (fourth entry in core options)? It's currently set to 2, and if removed from the configuration file with darktable stopped, will revert to 2 when darktable gets restarted and closed next time. Note I see t

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Matthias Andree
Am 09.04.2017 um 16:38 schrieb Ulrich Pegelow: > Am 09.04.2017 um 11:00 schrieb Matthias Andree: >> Am 08.04.2017 um 14:29 schrieb Ulrich Pegelow: >> 2. What bothers me though are the timeouts and their defaults. In >> practice, the darktable works ok-ish, but the lighttable does not. When >> a tru

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Ulrich Pegelow
Am 09.04.2017 um 11:00 schrieb Matthias Andree: Am 08.04.2017 um 14:29 schrieb Ulrich Pegelow: 2. What bothers me though are the timeouts and their defaults. In practice, the darktable works ok-ish, but the lighttable does not. When a truckload full of small thumbnails (say, lighttable zoomed out

Re: [darktable-dev] OpenCL scheduling profiles

2017-04-09 Thread Matthias Andree
Am 08.04.2017 um 14:29 schrieb Ulrich Pegelow: > Hi, > > I added a bit more flexibility concerning OpenCL device scheduling > into master. There is a new selection box in preferences (core > options) that allows to choose among a few typical presets. > > The main target are modern systems with very

[darktable-dev] OpenCL scheduling profiles

2017-04-08 Thread Ulrich Pegelow
Hi, I added a bit more flexibility concerning OpenCL device scheduling into master. There is a new selection box in preferences (core options) that allows to choose among a few typical presets. The main target are modern systems with very fast GPUs. By default and "traditionally" darktable d