Hi Terry, Am Mittwoch, 4. März 2015 02:22:25 UTC+1 schrieb Tduell: > > align_image_stack does indeed use all the cores for quite short periods of > > time, with periods in between where activity drops back to one core. When > > I run the script with calls to ais run as background tasks the cpu > activity peaks at 100% (all cores) for most of the time. > > thanks for checking. This matches the code: align_image_stacks does all calculation in multi-threading context. Only the image loading is single threaded. This should be only short times. So I assume the used resource monitor has some problem to display the core usage in real-time.
Also your timing speak that align_image_stack is using all cores: Sequential execution: 40 s Parallel execution: 30 s This is an improvement of "only" 25 %. So 75 % of the time align_image_stack is already running at full throttle. Or an other calculation: in sequential execution each stack takes 10 s. But when running the processes parallel it takes 30 s to calculate the same stack. The massive parallel execution of several align_image_stack can so even slower than the sequential execution when bigger and/or more images are used. Then the memory usage become the bottleneck. Thomas -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/26334c52-8d32-41b6-b9ba-b962c3d48d7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
