Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Apps and Programs
Multi Threading? App Specific.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mathogre" data-source="post: 568019" data-attributes="member: 25890"><p>The best one to answer it is the people who wrote the software. Write to them. Find a sales or customer support email address and send them the questions. They *should* be able to answer them.</p><p></p><p>That said, here's my guess.</p><p></p><p>The program probably allows you to specify the ability to use more than one thread, specifically up to four. Accordingly, when you're rendering an image, there will be at least four jobs running on your machine in support of the rendering. Four would run for the rendering job, and either one of those four or a fifth separate process would control the job.</p><p></p><p>Do you need four cores to do it? In theory if you had a four core machine, the application and OS could distribute the jobs among the cores. If you have two cores, you'd think two would work ideally. If you have only a single core machine, multithreading wouldn't be particularly appealing, at least on the surface. More on this next.</p><p></p><p>If the program is processor intensive - one thread can keep your CPU at 100% usage - then really you're looking at using one thread per core. You could run it in a multithread mode, spawning other render threads, but you'd be fighting against yourself. It would probably take longer to run, swapping jobs back and forth.</p><p></p><p>If the progam isn't taking the entire core all of the time, then you might be able to go with more than one thread per core. For instance, the program could be spending a considerable amount of time writing to disk. If so, you could potentially run 3 or 4 threads on a two core machine and realize some efficiency. Also, you could potentially run more than one thread on a single core machine. Still, my guess is that being a rendering program it will be very processor intensive, and you're probably looking at one thread, one core.</p><p></p><p>Hope this helps!</p></blockquote><p></p>
[QUOTE="mathogre, post: 568019, member: 25890"] The best one to answer it is the people who wrote the software. Write to them. Find a sales or customer support email address and send them the questions. They *should* be able to answer them. That said, here's my guess. The program probably allows you to specify the ability to use more than one thread, specifically up to four. Accordingly, when you're rendering an image, there will be at least four jobs running on your machine in support of the rendering. Four would run for the rendering job, and either one of those four or a fifth separate process would control the job. Do you need four cores to do it? In theory if you had a four core machine, the application and OS could distribute the jobs among the cores. If you have two cores, you'd think two would work ideally. If you have only a single core machine, multithreading wouldn't be particularly appealing, at least on the surface. More on this next. If the program is processor intensive - one thread can keep your CPU at 100% usage - then really you're looking at using one thread per core. You could run it in a multithread mode, spawning other render threads, but you'd be fighting against yourself. It would probably take longer to run, swapping jobs back and forth. If the progam isn't taking the entire core all of the time, then you might be able to go with more than one thread per core. For instance, the program could be spending a considerable amount of time writing to disk. If so, you could potentially run 3 or 4 threads on a two core machine and realize some efficiency. Also, you could potentially run more than one thread on a single core machine. Still, my guess is that being a rendering program it will be very processor intensive, and you're probably looking at one thread, one core. Hope this helps! [/QUOTE]
Verification
Post reply
Forums
Apple Computing Products:
macOS - Apps and Programs
Multi Threading? App Specific.
Top