2012/1/22 Martin Middelhoek <[email protected]>

> enblend starts 4 threads on my 4 core MacPro and does very briefly
> reach a CPU utilisation of 350%. The whole process is so fast that it
> is difficult get a good average result from the activity monitor.
> Blending 16 x 72MB (2800x4300 16bit) images takes a little more than
> 1.5 real minutes and 4 cpu minutes. This corresponds to 2.5 effective
> cores for the whole process. And best off all: no crashes.
>
> Martin
>

Just out of curiosity: If you run the same stitch with  the "old Tiger"
enblend: how long does that take?
I only mean the enblend process, not the entire process with nona as well.

Currently I do tests with the enblend 4.0, enblendhg and multiblend. To do
this I did a run from Hugin choosing only the positioned images.

Then from the command line I did a "time <enblend, enblendhg, multiblend>
-o something.tif test0*.tif"
The time shows the execution time (and some more) of the command.

Harry

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to