hugin-devs team mailing list archive

[rew <684859@xxxxxxxxxxxxxxxxxx>]

Someone wrote to tell me this is purely user-error: nona has a -t 1 option to restrict it to one thread. 
and hugin has a "make options" entry where I can set -j 2 to use two CPUs. 


** Changed in: hugin
       Status: Triaged => Fix Released

-- 
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:
  Fix Released

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 ?