Thanks, Maarten, but I wasn't the original poster. I was just responding
to E Kow and the list with the thoughts I've had.
On 1/11/24 23:12, Maarten Verberne wrote:
https://www.cpubenchmark.net/singleThread.html
maybe this helps you to find a speedy cpu for hugin.
I've already settled on that - Ryzen 7950X. Enblend and other graphics
applications I use really benefit from multiple cores and threads, so
the more cores, the better.
Since I want performance, Intel's continued love affair with efficiency
cores doesn't appeal to me. My experience with Intel performance
processors has been that while Intel loves to chant their peak clock
speeds, their processors can only hit that speed with a single core is
enabled. What's the point of that when the software happily and rapidly
uses multiple cores?
The i9 in my laptop has a nominal 5GHz max. The best it has ever done is
4.6GHz, and that only briefly before it throttled down due to temperature.
Op 12-Jan-24 om 8:52 schreef Maarten Verberne:
Hi David,
I do not know your working method, but a high end graphics card is
not really needed and won't improve speed that much since only nona
uses it for a split second.
recompiling hugin so enblend can use the gpu did not lead to a
speedincrease in my case, so i work now without -gpu in enblend...but
that might be different for you.
My working method is interactive. I don't do nearly as many images as
you do!
I have stitched about 2m images this year via cmd scripts.
depending on how much cores you have you might be able to start more
than one cmd process.
fi i use a ryzen 5-3600 for stiching and have 3 cmd script run
simultanious.
as for the -g (GPU use) for nona, i've discovered nona doesn't work
well with nvidea, even an intel IGPU is quicker...as is an AMD card.
I think nona uses OpenGL, which NVidia doesn't really support. NVidia
wants to lock customers into their platform; the antithesis of OpenGL.
Nona plus the on-board Intel UHD-630 works fine.
Another question to think about.
Multicore CPU: yes, many cores/threads. Start three processes, each gets
a core/thread.
Is the same true about GPUs? Or does a GPU handle input from only one
source at a time? So if script 1 fires off Nona on the GPU, what happens
when script 2 and script 3 try to run nona on the GPU at the same time?
lastly, my system used 3 HDDs (one for each cmd script that is
running) but an ssd would naturally help a bit there speedwise.
all in all it takes me about 1 week to process 160.000 images to 80.000
if you do find a way to speed that up, i'm very interested.
Maarten
Maarten, in my experience, replacing your HDD drives with SSDs would
make a big difference. Even connected via SATA cables, SSD is faster.
NVME drives (if your motherboard supports them) would be even faster.
If your motherboard doesn't support NVME, you might invest in a 4-port
PCIe expansion card that adds NVME connections, and replace your HDDs
with NVME SSDs on the card. I think it would massively increase read and
write speeds.
Op 12-Jan-24 om 5:04 schreef David W. Jones:
On 1/11/24 01:19, E Kow wrote:
Hi,
As mentioned earlier I am often stitching 500 or more microscope
images.
I am thinking to get a new dedicated computer for this.
How much computing power can Hugin utilize (RAM, GPU etc)?
Does it make sense to buy a really high spec desktop computer with
high end graphics card?
E Kow, if you're still reading this:
Go for as much processor performance and memory you can. Hugin spends
nearly all of its processing time running on the CPU and using memory.
Don't worry about the GPU. Intel or AMD on-board GPU is plenty. Nona is
the only part of Hugin that uses GPUs. Maarten is right. At worst, nona
only takes a tiny fraction of time to remap images using onboard Intel
UHD GPUs. No need to spend money for high-end, mid-level, or low-end GPUs.
Hello!
I don't know how much Hugin can utilize re RAM, GPU, etc, but I run
Hugin on a laptop with an 8-core/16-thread i9, 64GB of RAM, 2TB NVME
PCI drive. The laptop has two GPUs - Intel UHD630 and NVidia
GTX-1650 Max.
I run Linux and have never been able to get any application to use
the GTX, but the Intel GPU works fine for remapping images.
I've done some big panoramas - not as many frames as yours! - and
had the system consume more than 64GB of RAM. I don't think the RAM
consumption is related to processes running on a GPU. It comes when
Hugin goes to the blending process. Hugin happily runs 16 threads
and takes as much memory as it needs.
I'm giving up on laptops as power computing platforms. While modern
ones can pack fast processors and almost enough memory, they can't
dissipate heat fast enough. Throttling kicks in, and then a
processor capable of hitting a nominal 5GHz is running at 3GHz
instead, with a temperature reported at 212F.
For comparison, the 2-core, no-thread Pentium 4 in my server (in a
midsize desktop tower case) is set to run a constant 3GHz (and does)
and runs at 110F. It never throttles.
My current plans would be for an AMD 7950X, 128GB (256GB if
possible). My current camera shoots 20MPX and I prefer to work with
RAW and high-dynamic range. I'm hoping to replace with camera with a
61MPX Sony A7R IVA model, so I expect RAM consumption will go up a lot.
I don't know if the Windows version of Hugin supports NVidia GPUs
better than the Linux version does. I understand Linux supports AMD
GPUs better than the NVidia line.
I'm sure there are people on the list that know more about Hugin and
GPUs, maybe they have thoughts?
--
David W. Jones
[email protected]
wandering the landscape of god
http://dancingtreefrog.com
My password is the last 8 digits of π.
--
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/7888567c-8e50-4574-afce-9a5a9a11a502%40gmail.com.
