-
Notifications
You must be signed in to change notification settings - Fork 56
Speed Comparison
This page shows speed comparison when stitching panorama files using various options: GPU, no GPU, etc.
Tests were done using Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz with 16 GB of memory and NVIDIA 1080 graphics card (inno3D).
Hugin version: 2017.0.0.eac5e8cc546e.
Enblend version: 4.2 (no GPU support).
multiblend version: v0.6.2.
Linux: Arch Linux.
The time shown is the time given by the script itself (at the end). As a test sample of 10 images was used from first generation of Gear360. Only one run was done for each case (browser with YouTube in the background). Option -a is to enforce image processing, otherwise script would skip already processed files.
| No | Options | Time [s] (less is better) | Per image [s] (less is better) | Comment |
|---|---|---|---|---|
| 1 | -a *.JPG |
96 | 9.6 | GPU + enblend (default) |
| 2 | -a -m *.JPG |
46 | 4.6 | GPU + multiblend |
| 3 | -a -n *.JPG |
125 | 12.5 | No GPU + enblend |
| 4 | -a -n -m *.JPG |
75 | 7.5 | No GPU + multiblend |
Conclusion: using multiblend gives noticable advantage, but the quality suffers a little bit - expect stitching seams to be more visible. Disabling GPU usage also has some impact on the speed.
It would also be interesting to see test results with enblend and GPU support compiled in.