by all means do some tests. a single pipeline will lock a single GPU device
for itself. running a second instance of darktable in parallel with opencl
enabled, too, is likely to cause some major confusion and result in
out-of-memory errors.
but for the cpu code path you might be able to overschedule a little to get
rid of an odd scaling problem or another as for instance for compressing to
your output format, syncing the buffers in between two modules. by default
dt will use all your cores, maybe you want to limit it via OMP_NUM_THREADS
to 4 on a 32 core machine and run 9 processes in parallel, assuming you
have /a lot/ of ram.
-jo
On Fri, Mar 13, 2015 at 7:39 AM, Markus Jung <maju.j...@web.de> wrote:
> darktable uses parallelisation internally for (at least almost) every
> image operation. Most likely you do not want to run multiple darktable
> instances in parallel (memory bandwidth, cache locality, but i recommend
> you to do a few test-runs.
>
> Regards,
> Markus
>
> Am 12.03.2015 um 19:19 schrieb Matt Kitcat:
> > Hello all.
> > I was wondering what sort of spec I should be looking for when choosing
> machines to render raw frames to openEXR from the command line only. Should
> I be going for high end graphics cards or concentrate more on ram and
> processor power.
> > In the old days of dcraw I used to limit the maximum number of images to
> process to slightly fewer that the number of cores. So on an 8 core machine
> I would limit it to 6 images at one time. This seemed to be the most
> efficient in terms of speed/image throughput. I am not sure how Darktable
> manages multicore processors and what sort of policy I should adopt. I want
> to achieve the maximum number of images per minute so I would be interested
> in peoples thoughts.
> >
> > Many thanks
> >
> > Matt
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> > by Intel and developed in partnership with Slashdot Media, is your hub
> for all
> > things parallel software development, from weekly thought leadership
> blogs to
> > news, videos, case studies, tutorials and more. Take a look and join the
> > conversation now. http://goparallel.sourceforge.net/
> >
> >
> >
> > _______________________________________________
> > Darktable-users mailing list
> > Darktable-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/darktable-users
> >
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Darktable-users mailing list
> Darktable-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users
