Gnome Nomad | 18 Jun 2012 02:20
Picon

Hugin ignoring the number of processors settings?

Hugin version 2011.4.0.cf9be9344356 on Debian Sid 64-bit running on AMD 
Phenom II 4-core processor. Previous version of hugin used multiple 
cores for cpfind without me setting anything about number of processors 
to use. This version set itself to use only 1 processor. I edited 
preferences and set number of processors to 4. Closed Hugin, restarted 
it, the # of processors value is still 4, but it's still only using 1 
processor when running CPfind (can see this in HTOP).

Makes thing a lot slower than they used to be!

Other programs that use multiple cores (such as Rawtherapee) use all 
four cores (even hyperthreading on most of them).

Is this Hugin or CPFind's issue?

-- 
Gnome Nomad
gnomenomad <at> gmail.com
wandering the landscape of god
http://www.clanjones.org/david/
http://dancing-treefrog.deviantart.com/
http://www.cafepress.com/otherend/

--

-- 
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 hugin-ptx <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
(Continue reading)

Harry van der Wolf | 18 Jun 2012 10:51
Picon

Re: Hugin ignoring the number of processors settings?

Hi,

2012/6/18 Gnome Nomad <gnomenomad <at> gmail.com>
Hugin version 2011.4.0.cf9be9344356 on Debian Sid 64-bit running on AMD Phenom II 4-core processor. Previous version of hugin used multiple cores for cpfind without me setting anything about number of processors to use. This version set itself to use only 1 processor. I edited preferences and set number of processors to 4. Closed Hugin, restarted it, the # of processors value is still 4, but it's still only using 1 processor when running CPfind (can see this in HTOP).

Makes thing a lot slower than they used to be!

Other programs that use multiple cores (such as Rawtherapee) use all four cores (even hyperthreading on most of them).

Is this Hugin or CPFind's issue?

What happens if you specify the  "-n <int>" or "--ncores <int>" in the cpfind parameters in Preferences->CP detectors?
cpfind should normally design automatically how much processes to use but maybe this automatic feature is not good enough.
I don't know whether the hugin parameter is promoted to cpfind or any other (possibily exotic) CP detector.

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 hugin-ptx <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
Gnome Nomad | 19 Jun 2012 11:52
Picon

Re: Hugin ignoring the number of processors settings?

On 06/17/2012 10:51 PM, Harry van der Wolf wrote:
> Hi,
>
> 2012/6/18 Gnome Nomad <gnomenomad <at> gmail.com <mailto:gnomenomad <at> gmail.com>>
>
>     Hugin version 2011.4.0.cf9be9344356 on Debian Sid 64-bit running on
>     AMD Phenom II 4-core processor. Previous version of hugin used
>     multiple cores for cpfind without me setting anything about number
>     of processors to use. This version set itself to use only 1
>     processor. I edited preferences and set number of processors to 4.
>     Closed Hugin, restarted it, the # of processors value is still 4,
>     but it's still only using 1 processor when running CPfind (can see
>     this in HTOP).
>
>     Makes thing a lot slower than they used to be!
>
>     Other programs that use multiple cores (such as Rawtherapee) use all
>     four cores (even hyperthreading on most of them).
>
>     Is this Hugin or CPFind's issue?
>
>
> What happens if you specify the "-n <int>" or "--ncores <int>" in the
> cpfind parameters in Preferences->CP detectors?

CPFind uses all 4 cores.

> cpfind should normally design automatically how much processes to use
> but maybe this automatic feature is not good enough.

It used to be. I never had to set the number of cores before, it just 
used them.

> I don't know whether the hugin parameter is promoted to cpfind or any
> other (possibily exotic) CP detector.

I don't know, I only use CPFind now.

linefind only seems to use 1 core, too, I'd think it could be able to 
use 4 cores, since it's also analyzing a single image at a time?

-- 
Gnome Nomad
gnomenomad <at> gmail.com
wandering the landscape of god
http://www.clanjones.org/david/
http://dancing-treefrog.deviantart.com/
http://www.cafepress.com/otherend/

--

-- 
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 hugin-ptx <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx


Gmane