This article relates to the fractal program "Apophysis" (Apo), but may also be relevant to other image rendering programs.
In Apo, there is a setting in the OPTIONS menu where one can specify the number of rendering "threads" to use. This has a direct impact on the amount of rendering time an image takes to render. If set to OFF, the image will render as if it was using a single CPU. If set to 2 or 4, the image will render in much less time, because it has 2 or 4 CPU cores of which to take advantage.
People who have Intel CPUs, which have hyperthreading (such as some Pentium 4's), can set this option to 2 if they wish (DO NOT use higher than 2).
Don't know how to get an image in here, so here is the screenshot link showing this setting option.
[link] Hyperthreading (wanky marketing speak), basically means the CPU has "two threads" with which to perform its data processing (sort of like two CPUs). When set to 2, Apo can use 100% of the CPU and thus cut rendering time. However, this may not be the best option with systems which generate a lot of heat and are not efficiently cooled (some laptops/notebooks may be an issue). It can be a trade-off between less render-time, OR a processor working at half its capacity and therefore producing less heat. System crashes can be a result of the processor over-heating.
If you have a newer system with either an AMD or Intel Dual-core processor, or for those fortunate people who may have a quad-core, then you should definitely set this option to correspond with the number of cores in your processor. There should be no problem with over-heating, as these newer processors have more efficient thermal designs than the older Pentium 4's.
I am running a Pentium 4 which has hyperthreading and I have set the multithreading option to 2. It can sometimes halve the rendering time, but always results in a substantial reduction.
The other thing I notice is the drop-down box below the multithreading box, which relates to both your CPU and operating system. Newer CPUs (from around mid-2003 for AMD and later for Intel) are 64bit. Prior to this they were 32bit. If your CPU and operating system are both 64bit, then I also suggest choosing the 64bit setting. I don't know the impact of this (mine is 32bit), but you will find out once you switch between the 32 and 64bit settings.
Here is the screenshot link showing this setting option.
[link]To test the impact of changed settings, you need to commence a render on the old settings. At the bottom of the render screen, the "estimated time to complete" will appear. Take note and STOP the render, then close it. Go back into OPTIONS and change the settings then commence the same render. Now you should see the time to complete has considerably reduced.
Steve Knorr
Result: super good rendering time.
I am using apophysis 7x on win 7 / 64bit.
32/64 bit doesn't really change rendering time, but 64bit seems to create a bit more lag for mouse etc..i am not sure.
interesting that 32/64 create a different file (not the same size).
--
Check out my DA profile page: [link]
--
"Icy roads beneath my feet led me through wastelands of deceit. Rest your head now, don't you cry; Don't ever ask the reason why." ~Opeth
--
~~~~~~~~~~~~~~~
when in doubt....Smile
=]
~~~~~~~~~~~~~~~
--
#GetWatchers - Need Exposure, Watchers, Views? Join us here!
--
Developer of Apophysis 7X
Loyal fractal warrior of the Aposhack
Moderator of #FracStract and #Apophysis
http://protocol.by/xyrus02
--
To love whatever fate brings our way.
Member of
~fractalers *Apophysis ~belgium *PhotographersClub *Ex-po-zure *sony-club =ImagersFractalDDs *macro-club *FractalDreams *wildlifephotography =NaturPics-club
My understanding, is that the multithreading number set in the *context of Apo*, equates to how many threads your processor can process at any one time. And in the case of dual core, each "processor" processes one thread, which means it can process two (being dual core). If you had a quad core processor, then you could choose the "4" setting. But again, I can't say to what degree this would have on rendering time, as I don't have either dual core or quad core processors.
Multithreading is actually more complex than this, because lots of software programs can run using multiple threads. This means a CPU may be processing multiple threads, regardless of the number of cores it has. But that's a whole other layer of complexity which you can read about on the Net.
Apo needs only a certain amount of Ram to be available for both the software and render. Depending on the quality and resolution of the render, it may need additional Ram to be available. Beyond that requirement, additional Ram is superfluous to the program, so you won't see any gain in time saved by having a greater amount of Ram available. It is only advantageous if you are simultaneously running Ram hungry programs. But 2gig is a nice amount of Ram to have in todays systems!
A question... if you render something with the multithreading setting at 2 and 32 bit, and then render the same thing with the bit setting at 64, does the render time reduce further, or does it make no difference? I am just trying to understand whether the bit setting affects render time, or whether it is just the multithreading setting that influences the render time.
--
Apophysis [link]
To illustrate:
Multithreading off
internal buffer depth 32 bit integer:
-> buffer depth integer 32 integer: 6h19
-> 32 floating: 6h20
-> 48: 6h25
-> 64: 6h24
Multithreading off
internal buffer depth 64 bit:
-> 32 integer: 6h52
-> 32 floating: 6h19
-> 48: 6h25
-> 64: 6h24
Multithreading 2 seems to give more or less the same rendering times in every combination (3h20 more or less), although 64bit in the rendering window does require twice as much RAM. In all the cases, 100% of my CPU is taken though, which seems a bit strange, because the amount of RAM necessary is waaaay below what I have available. (Although running other programs at the same time doesn't seem to slow the rendering down much.)
As for having a 32 bit operating system... I had ordered a 64 bit one but they got one in the wrong language, and they only had 32 bit in the right language. And in the shop they said it didn't matter. After some research it might be best, apparently there are some problems with compatibility with 64bit Vista (only accepts 64 bit drivers, not 32 bit drivers), but I'm no expert. At the same time I am wondering if having a 64 bit OS would halve the rendering time again, but I guess we'd have to ask someone who has a 64 bit OS.
*sigh* I don't know enough on all this tech stuff, that's why I gave this overload of info
--
To love whatever fate brings our way.
Member of
~fractalers *Apophysis ~belgium *PhotographersClub *Ex-po-zure *sony-club =ImagersFractalDDs *macro-club *FractalDreams *wildlifephotography =NaturPics-club