Force Revit to use multiple cores?

[Anonymous]

When exporting files from Revit to softwares like ETABS or Robot Structure Analysis, Revit makes use of only 1 core.

Is there any way to force it to make use of all 8 cores of my CPU?

[Avaris.]

No, sorry. It is the way Revit developed it.

[Anonymous]

Is this for real?

A multi-million dollar company is not able to launch a software with something as simple as multi-core support?

I pay my money to you, lots of it, and I even run an AutoDesk Authorised Training Centre.

I create future customers of AutoDesk products and I cannot get a simple feature that can make my student's learning process faster?

Even Revit Extensions 2019 is not available yet.

Has AutoDesk taken a turn for the worst?

[Avaris.]

That is for real. Only a few things are multi-threaded. If you want to have more, vote for more multi-threaded processes.

[Corsten.Au]

Hello

Go to Task Manager, 

Go to Details

Right Click Revit.exe, and use " Set Affinity "

Processor Affinity.

[Anonymous]

It will still only run on one core....

But...if  you have multiple sessions running you can specify a core for each session.  I used to do this quite a while back, but eventually found out it wasn't worth the hassle.

[ToanDN]

It wasn't particularly useful unless you ran a rendering in a session and wanted to limit it to a certain number of cores so that you would still have some free cores to mess around or whatever.

[SteveKStafford]

More is always better? If one core is good then many must be better? The developers I've talked to have explained that such logic is counter intuitive. Not all of software operations are distributed well across multiple cores. Rendering is one that is because tasks can be distributed and reassembled. I find the performance in the last three releases has been considerable and most of it has nothing to do with multi-threading at all.

[adrian.esdaile]

---

@Avaris. wrote:

That is for real. Only a few things are multi-threaded. If you want to have more, vote for more multi-threaded processes.

---

Excuse me? Vote for more multi-threaded processes? 

How about: We pay a FORTUNE for this software, with our data locked-in, so how about Autodesk give us our money's worth by actually making software that is more sophisticated than 2006-era performance

How about: If it can magically be done if users VOTE for it - why hasn't it been done already? We've only been asking for it for 15 years! If it's that EASY - why is it not already implemented?

How about: Autodesk listens to CUSTOMERS rather than SHAREHOLDERS.

This post was typed and edited while I waited for ONE SINGLE VIEW to regenerate while Revit used a massive 3.4% of my 20-core machine. 10 minutes of my life WASTED, thanks, Autodesk!

[adrian.esdaile]

Running multiple sessions of Revit is like running with scissors; one day you'll do yourself an injury.

If you're using workset files running multiple instances is a recipe for major work loss as each session can't keep track of it's own temp files properly.

It would be nice if Autodesk spent some of our ransom money  fire insurance  subs on proper coding...

[KrisAribal]

---

@adrian.esdaile wrote:

---

If it's that EASY - why is it not already implemented

---

It's not easy. There's a discussion on some programming forum ( I think it's an adobe forum) that if you want all the functions of a program to support multi-core or multi-thread you're basically creating the program from scratch. That would take a lot of time. Not to mention the tons of  bugs that comes with it  

[RobDraw]

---

@adrian.esdaile wrote:

---

---

This post was typed and edited while I waited for ONE SINGLE VIEW to regenerate while Revit used a massive 3.4% of my 20-core machine. 10 minutes of my life WASTED, thanks, Autodesk!

---

Someone doesn't know how to multi task is asking about using multiple cores?

Talk about blowing smoke...

[nmarcelis]

Aside from the single/multicore topic, It seems that you bought the wrong hardware. 
That way Revit works now is depending on the task single or multicore. Maby in the futher other parts will become  multicore. Regarding the export of dwg and pdf, take a look at RTV Xporter from RTV tools.

There are ways to automize the exports of drawings completely autonomous. 

[loboarch]

---

@SteveKStafford wrote:

More is always better? If one core is good then many must be better? The developers I've talked to have explained that such logic is counter intuitive. Not all of software operations are distributed well across multiple cores. 

---

I would echo this. I have heard developers say the same things.

The nature of the math involved in Revit parametric change ability is linear. The equation has to be processed much like a train running through a station on one track. The math involved makes it not possible to break this up and process separately and reassemble on the other side. Using multi-cores is fundamentally not possible because of the underlying math.

This is not true for EVERY facet of Revit and multi-cores has been enabled in some areas, but in other areas the opportunities are limited because of the nature of the math.  

[nmarcelis]

This is not true for EVERY facet of Revit and multi-cores has been enabled in some areas, but in other areas the opportunities are limited because of the nature of the math.  

---

@loboarch wrote:

---

@SteveKStafford wrote:

More is always better? If one core is good then many must be better? The developers I've talked to have explained that such logic is counter intuitive. Not all of software operations are distributed well across multiple cores. 

---

I would echo this. I have heard developers say the same things.

The nature of the math involved in Revit parametric change ability is linear. The equation has to be processed much like a train running through a station on one track. The math involved makes it not possible to break this up and process separately and reassemble on the other side. Using multi-cores is fundamentally not possible because of the underlying math.

This is not true for EVERY facet of Revit and multi-cores has been enabled in some areas, but in other areas the opportunities are limited because of the nature of the math.  

---

This should be pinned answer/quote on the majority of the singlecore/multicore discussions.
Sometimes what we want today isn't technologically possible.

[Anonymous]

---

@adrian.esdaile wrote:

Running multiple sessions of Revit is like running with scissors; one day you'll do yourself an injury.

If you're using workset files running multiple instances is a recipe for major work loss as each session can't keep track of it's own temp files properly.

It would be nice if Autodesk spent some of our ransom money  fire insurance  subs on proper coding...

---

Been running multiple sessions since release 8....never had any issues, even on workshared models.

[SteveKStafford]

I've used multiple sessions for a single project many times too...but I also run with scissors. It's not really any different than two separate users, separate sessions of Revit are compartmentalized within Windows. If it's risky...it's risky with one session. The significant risk is doing so with too little RAM.

[Anonymous]

Yep...RAM is something to be aware of when running multiple sessions. Since getting 32GB-64GB it's usually not thought of....but way back in the XP days it was thought about each time I opened a model.