Computer power for stacking
Moderators: rjlittlefield, ChrisR, Chris S., Pau
Computer power for stacking
Which features matter more?
I know the answers contain processor speed, followed by amount of memory, but in the periodic computer replacement, ever more variables appear.
I know Zerene can handle multiple cores, and needs about 100MB per megapixel.
So 4GB will cope with 40MB, but 8GB allows spare.
What about processors?
Is it better to have 2 faster cores or 4 slower?
Does processor speed lead proportionally to - anything?
Memory also comes in eg 1333MHZ and 1600MHz. Does that 20% increase lead to 20% or 1% overall?
I notice from my "console" that a lot of time is spent opening and closing files. Presumably this means a faster hard drive would help? Solid State Drive better? (High failure rates though?)
Here's a bunch of current options, for a laptop
- where the bang per buck is lower -
up to eg, for desktops..
Of course there are many in between, and AMDs, too.
All rather bewildering. Any guidance would be appreciated!
I know the answers contain processor speed, followed by amount of memory, but in the periodic computer replacement, ever more variables appear.
I know Zerene can handle multiple cores, and needs about 100MB per megapixel.
So 4GB will cope with 40MB, but 8GB allows spare.
What about processors?
Is it better to have 2 faster cores or 4 slower?
Does processor speed lead proportionally to - anything?
Memory also comes in eg 1333MHZ and 1600MHz. Does that 20% increase lead to 20% or 1% overall?
I notice from my "console" that a lot of time is spent opening and closing files. Presumably this means a faster hard drive would help? Solid State Drive better? (High failure rates though?)
Here's a bunch of current options, for a laptop
- where the bang per buck is lower -
up to eg, for desktops..
Of course there are many in between, and AMDs, too.
All rather bewildering. Any guidance would be appreciated!
It all comes down to bottlenecks, what's the weakest link in the chain. In any given configuration it will likely be one of two things, processor grunt or memory bandwidth (I'm going to simply assume you have _enough_ memory!). Tweak one up and the other could become the weakest link at which point continuing to improve the same one won't make any difference.
(But seriously, probably four as long as they're not significantly slower)
I don't know enough to comment on SSDs, I've considered getting one for my system disk and surely will do at some point but I haven't yet seriously considered using them for data drives. I have too much data...
I'd personally be looking for as many cores as possible. I'd tend towards AMD because their 6-8 core processors are pretty cheap compared to the Xeons iirc. Stack in at least 8gb or even 12 or 16, and make that memory as fast as possible assuming the mobo you choose can utilise it at that speed.
If that's your bottleneck then yes more would be better.Does processor speed lead proportionally to - anything?
How much faster/slower?Is it better to have 2 faster cores or 4 slower?
(But seriously, probably four as long as they're not significantly slower)
Somewhere between the two?! - If this is the bottleneck in your system then obviously more=better, though I doubt you'd ever see the figure you get from simply dividing one speed by the other..Memory also comes in eg 1333MHZ and 1600MHz. Does that 20% increase lead to 20% or 1% overall?
I don't know enough to comment on SSDs, I've considered getting one for my system disk and surely will do at some point but I haven't yet seriously considered using them for data drives. I have too much data...
I'd personally be looking for as many cores as possible. I'd tend towards AMD because their 6-8 core processors are pretty cheap compared to the Xeons iirc. Stack in at least 8gb or even 12 or 16, and make that memory as fast as possible assuming the mobo you choose can utilise it at that speed.
This is an interesting thread; as my next goal is to update my computer.
I am working with 21mpx 16bit TIFF files and my Core2Quad @ 2.83 Mhz with 4GB RAM seems dead slow; however I think I am getting better results,specially regarding colour.
I plan to update to a 6 core i7 but an i7 2600K would give you twice the performance I am getting now
Also plan to add an SSD for system files and another one for current Zerene projects
Regards
I am working with 21mpx 16bit TIFF files and my Core2Quad @ 2.83 Mhz with 4GB RAM seems dead slow; however I think I am getting better results,specially regarding colour.
I plan to update to a 6 core i7 but an i7 2600K would give you twice the performance I am getting now
Also plan to add an SSD for system files and another one for current Zerene projects
Regards
I can not tell now because I am doing a stack but files are already aligned; with files aligned 10 sec/eachChrisR wrote:How fast is dead?
Perhaps we could all compare notes
For 18MB 8 bit pictures my current speed is about one minute per exposure, for Pmax.
There's a whole spectrum of deadness
We could say my computer is dead slow and yours died long ago ;-)
I would say processor uis the most important part of the ecuation,
8GB of RAM are not expensive now and I would say a fast HDD to be also very important, specially if you work with large files like I do
Regards
-
- Posts: 233
- Joined: Thu Jan 05, 2012 9:10 am
- Contact:
Last time I checked, video work took much more advantage of multiple cores than Photoshop did. Above 2 cores Photoshop didn't see much of an advantage. I'm not sure what's the case with stacking software.
When I build a computer, I usually buy high value parts in the upper tier, but not cutting edge, as you have to pay a huge premium for that.
More memory is a terrific investment for photo work, with more memory being a better value than less (but super fast) memory.
When I build a computer, I usually buy high value parts in the upper tier, but not cutting edge, as you have to pay a huge premium for that.
More memory is a terrific investment for photo work, with more memory being a better value than less (but super fast) memory.
- Craig Gerard
- Posts: 2877
- Joined: Sat May 01, 2010 1:51 am
- Location: Australia
Chris,
I built a computer using compiled parts about a year ago. Inside the box I have an Intel i7 2600K (Quad Core) CPU, 16Gb of RAM, two 120Gb OCZ Vertex 3 Max IOPS SSD drives, one for system/programs files and another for storing files for use with current stacking projects. The SSD does reduce stack processing time by approximately 1 minute per 40 frames as opposed to the same stack with source files on a HDD. I also have a bank of standard HDD inside and outside of the main box.
Over the course of the past year the system has not missed a beat. It is very fast and responsive no matter how demanding the task. OS is Windows 7 64Bit.
Craig
I built a computer using compiled parts about a year ago. Inside the box I have an Intel i7 2600K (Quad Core) CPU, 16Gb of RAM, two 120Gb OCZ Vertex 3 Max IOPS SSD drives, one for system/programs files and another for storing files for use with current stacking projects. The SSD does reduce stack processing time by approximately 1 minute per 40 frames as opposed to the same stack with source files on a HDD. I also have a bank of standard HDD inside and outside of the main box.
Over the course of the past year the system has not missed a beat. It is very fast and responsive no matter how demanding the task. OS is Windows 7 64Bit.
Craig
To use a classic quote from 'Antz' - "I almost know exactly what I'm doing!"
Chris,
Like Craig, I also have an Intel i7 2600K CPU. 16 Gb RAM (Default 3 Gb allocated to Zerene Stacker). Separate hard drives for system and data, Western Digital Caviars. Windows 7, 64-bit.
15 mpix 8 bit TIFF (from Canon 50D) stacks at 3.8 seconds/frame (ZS PMAX). CPU usage as measured by Windows Task manager averages around 40%.
Jörn
Like Craig, I also have an Intel i7 2600K CPU. 16 Gb RAM (Default 3 Gb allocated to Zerene Stacker). Separate hard drives for system and data, Western Digital Caviars. Windows 7, 64-bit.
15 mpix 8 bit TIFF (from Canon 50D) stacks at 3.8 seconds/frame (ZS PMAX). CPU usage as measured by Windows Task manager averages around 40%.
Jörn
- Craig Gerard
- Posts: 2877
- Joined: Sat May 01, 2010 1:51 am
- Location: Australia
*I noticed Jörn has responded while I was typing my response. The Western Digital Caviars are good drives.
Chris,
I wouldn't consider anything other than an OCZ Vertex 3 Max IOPS SSD for the system drive. No matter how fast your CPU nor RAM capacity a HDD system drive will always be a bottleneck.
I've looked closely at a post I made some time ago comparing the processing time of a stacking project using an SSD and a HDD.
The "1 minute per 40 images" indicated in my previous response was an guesstimate. The stacks are processed at such an acceptable speed that I have not bothered to time them since.
Here are some details of a system comparison, reference thread link below quotes.
*There has been a minor reduction in stack processing times (a matter of 10's of seconds) when the source files are located on a separate SSD secondary to the system file SSD. As I've mentioned, I have not timed the process recenty because it works so well I've had no reason determine actual timings.
Craig
Chris,
I wouldn't consider anything other than an OCZ Vertex 3 Max IOPS SSD for the system drive. No matter how fast your CPU nor RAM capacity a HDD system drive will always be a bottleneck.
I've looked closely at a post I made some time ago comparing the processing time of a stacking project using an SSD and a HDD.
The "1 minute per 40 images" indicated in my previous response was an guesstimate. The stacks are processed at such an acceptable speed that I have not bothered to time them since.
Here are some details of a system comparison, reference thread link below quotes.
The following test was conducted before I received my second SSD which I now use primarily for holding focus stack source images for feeding to Zerene.I've plugged most of the new 'bits' in and ran a timing comparison PMax focus stack in Zerene Stacker
All Alignment Preferences (Shift X, Shift Y, Scale, Rotation, Brightness, Automatic order were checked 'ON').
The same set of images, source drive and parameters were used for both stacks.
Intel Q6600 Core 2 Quad: 106 images 4752 x 3169px (16bit tif): Time = 16 minutes and 15 seconds.
Intel Core i7 2600K (Quad): 106 images 4752 x 3169px (16bit tif): Time = 7 minutes and 30 seconds.
Reference:http://www.photomacrography.net/forum/v ... hp?t=13028For reference.
I ran a Zerene PMax focus stack directly from the Primary SSD (source files on SSD (OS and program files on same SSD)).
All Zerene Stacker options > Preferences > Alignment 'ON'.
Intel Core i7 2600K (Quad): 106 images 4752 x 3169px (16bit tif): Time = 6 minutes and 32 seconds.
Equates to approx. 1 minute less than the previous test where the source files were located on a secondary 'platter' 7200 rpm HDD.
It will be interesting to see if there is much difference repeating this exercise when the source files are located on a separate SSD. I don't expect there will be....
*There has been a minor reduction in stack processing times (a matter of 10's of seconds) when the source files are located on a separate SSD secondary to the system file SSD. As I've mentioned, I have not timed the process recenty because it works so well I've had no reason determine actual timings.
Craig
To use a classic quote from 'Antz' - "I almost know exactly what I'm doing!"
- rjlittlefield
- Site Admin
- Posts: 23937
- Joined: Tue Aug 01, 2006 8:34 am
- Location: Richland, Washington State, USA
- Contact:
I have an Intel Core 2 Quad Q6600, 2.40 GHZ. Just now re-ran an old stack (already aligned), using Options > Preferences > Multiprocessing set to 4, 2, and 1 core. (This is actually the number of computational threads. Garbage collection if any may still use another processor when #procs < hardware limit.)JB wrote:Chris,
Like Craig, I also have an Intel i7 2600K CPU. 16 Gb RAM (Default 3 Gb allocated to Zerene Stacker). Separate hard drives for system and data, Western Digital Caviars. Windows 7, 64-bit.
15 mpix 8 bit TIFF (from Canon 50D) stacks at 3.8 seconds/frame (ZS PMAX). CPU usage as measured by Windows Task manager averages around 40%.
Jörn
15 Mpx JPEG, 82 frames, already aligned, ran at:
1 proc, 14:15
2 proc: 10:35
4 proc: 7:38 (~5.6 seconds per frame)
Parallel efficiency here is about 46% -- 4 processors makes the thing run a little less than twice as fast.
If you want to crank up the efficiency, and have enough memory to keep all processes resident in RAM, then consider running two or more stacks at the same time. In testing just now on my machine that cranks up the utilization someplace above 80%.
--Rik
Edit: to note already aligned
Last edited by rjlittlefield on Sat Apr 28, 2012 2:32 am, edited 1 time in total.
Just to specify conditions,
When I purchased my computer parts July 2011, the i7 2600K seemed to be a "sweet spot" when comparing price to performance.
No doubt SSD drives would have been a faster option than my conventional Caviars. But at that time I found the price difference too large. Considering my data drive is from Western Digitals "Green" line and runs at (only) 5400 rpm, I find the performance very respectable.
Like Rik mentions, it is possible to increase efficiency by running more than one Zerene Stacker session at a time, but I don't really feel the need for it. When ZS utilizes only around 40% CPU, it is possible to work in Photoshop or do other things while stacking in the background; I find that very convenient.
If one gets intolerably impatient, there is always the option of walking away from the computer for a few minutes - which is very healthy ;-)
Jörn
This result includes alignment. If the frames have already been aligned, stacking is around 2.0 seconds/frame under the same conditions.I wrote:Chris,
Like Craig, I also have an Intel i7 2600K CPU. 16 Gb RAM (Default 3 Gb allocated to Zerene Stacker). Separate hard drives for system and data, Western Digital Caviars. Windows 7, 64-bit.
15 mpix 8 bit TIFF (from Canon 50D) stacks at 3.8 seconds/frame (ZS PMAX). CPU usage as measured by Windows Task manager averages around 40%.
Jörn
When I purchased my computer parts July 2011, the i7 2600K seemed to be a "sweet spot" when comparing price to performance.
No doubt SSD drives would have been a faster option than my conventional Caviars. But at that time I found the price difference too large. Considering my data drive is from Western Digitals "Green" line and runs at (only) 5400 rpm, I find the performance very respectable.
Like Rik mentions, it is possible to increase efficiency by running more than one Zerene Stacker session at a time, but I don't really feel the need for it. When ZS utilizes only around 40% CPU, it is possible to work in Photoshop or do other things while stacking in the background; I find that very convenient.
If one gets intolerably impatient, there is always the option of walking away from the computer for a few minutes - which is very healthy ;-)
Jörn
This is the kind of computer I want to go for; I am seriously thinking of I7 3930K but also two SSD and 16GB RAM, just like youCraig Gerard wrote:Inside the box I have an Intel i7 2600K (Quad Core) CPU, 16Gb of RAM, two 120Gb OCZ Vertex 3 Max IOPS SSD drives, one for system/programs files and another for storing files for use with current stacking projects.
Also very interesting; how much memory is enough for two 21mpx stacks?rjlittlefield wrote:If you want to crank up the efficiency, and have enough memory to keep all processes resident in RAM, then consider running two or more stacks at the same time. In testing just now on my machine that cranks up the utilization someplace above 80%.
I have just run a test stack of 30 21mpx JPG images and the whole operation to make the Pmax took 6:03; individual images averaging 11/12 sec
As I said before my computer is a core2Quad 9550 @2.83 with 4GB RAM windows 7 64 bit
Regards
- rjlittlefield
- Site Admin
- Posts: 23937
- Joined: Tue Aug 01, 2006 8:34 am
- Location: Richland, Washington State, USA
- Contact:
Twice as much as for one. ZS minimally takes 1551 MB for 21.0 mpx; a little more is better, say 2100 MB. So, running two in 4 GB would be very tight and might not work due to paging induced by other processes. But 6 GB or 8 GB should be fine.seta666 wrote:Also very interesting; how much memory is enough for two 21mpx stacks?
--Rik