← Back to team overview

hugin-devs team mailing list archive

[Bug 684859] Re: Nona phase should use all CPUs on big stitch

 

The first can be achieved by setting "MAKEFLAGS=-j 2" or higher.
The second one is also already possible: run nona with -t 1
See description in the help on panotools: http://wiki.panotools.org/Panorama_scripting_in_a_nutshell#Parallel_make

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/684859

Title:
  Nona phase should use all CPUs on big stitch

Status in Hugin - Panorama Tools GUI:
  Triaged

Bug description:
  Although nona is said to use all available CPUs, my CPU graph shows otherwise. 

The issue is that when i'm working on a big project (where i'd expect the multi-cpu to be extra useful), the images are downscaled significantly. Thus the phase that nona executes multi-cpu is short. The single-threaded pre and post processing take up about half the time. 

As I have plenty of memory I'd gladly tell make to start two or three concurrent nona processes to keep my CPU busy. 

Suggestion: preference setting: how many nona processes should run concurrently ?





References