Slow have to wait several minutes between CLICKS

[Mufasa23]

I will click after command initiation, and then I will have to wait several minutes (really MINUTES) before my system will finish "thinking" to allow me to perform another command. My system is: 6 core processor 3.5 GHz, Win 10 Pro, 32 GB RAM, 64 bit and running a stand alone version of 2016 vanilla.
Is there anyone with advice on how to speed my system? I'm DYING !
thanks
JT

[Tom Beauford]

Is the drawing saved on your local drive or on the network? How quick is the Line command? My PC is screaming fast now, but referencing GIS data on the network takes forever.

[Ed Jobe]

Is it always this way? You don't provide much info to troubleshoot with. Have you tried rebooting? If you go to Windows Task Manager and click on the Processes tab (sort on CPU), it can tell you if some other process is slowing you down.

[Mufasa23]

installed local, but the drawing file is on our network. "Line" command is no problem. It's definitely a sure thing for a long wait when I have the layers dialogue box open or switching in and out from block editor. Or sometimes something as simple as a move command.

- - - Updated - - -

Yes, been tormenting me for a long time. Even if I reboot it's not helpful. I've been in task mgr and AutoCAD is the biggest strain. Topping my memory usage at 26%. Not really an issue but a good idea.

[Tom Beauford]

I draw everything on a local drive and copy it to the network afterwards to share. If you can do your work 5 times faster who's going to complain?

[Ed Jobe]

Same dwg? or all dwgs? You say "sometimes". That would indicate that this is an intermittent problem... Try to find a symptom that is consistent and reproducible.

When in task manager, 26% is low. Take note of what else is taking up the other 75%.

[MMccall]

I've had a weird scenario in the past at a small company with only two CAD machines. If one of the machines had a bad path location in their settings it would take both machines down to a crawl.

[CCarleton]

Can someone in your office check out the DWGs you struggle with and work at a faster rate? That'd be your #1 check to see if it's a you problem or a DWG problem. Also being on the network doesn't mean it will be slow, but it could be if you're referencing a DWG not in your office.

My company has several offices spread out around the state, and our IT department is ticketed from time to time complaining about slow DWGs. Since they're not CAD wizards they can't do much, but they'll tell them that they're communicating with a server not from their office (because they can see the network traffic). Sometimes it devolves into "No...I'm not working off that drive" to which they respond "Well ok dude, but I'm watching the other office's server send tons of information to your computer so you can tell me you're not, but your drawing is definitely doing something with that server." Eventually the realization becomes something along the lines of "Oh god, xref."

You shouldn't have a slow computer just because you're using a network's DWG, but if it, or anything it interacts with, is not on your office's server you will likely feel it to some degree. Additionally if your CAD references filepaths for settings on another server you could also be suffering from that as well.

And as Tom pointed out if you're in a big drawing with something like high res photos you are pretty much destined to be slow, regardless of being local or not.

You could also play with hardware acceleration by turning that on or off (which it currently isn't) and see if that does anything. I've seen some crazy things for some machines get solved by playing with it.

[Mufasa23]

thank you, good advice - will explore these options!

[Mufasa23]

Ed,
I haven't ben able to find the common denominator yet. It's driving me crazy. The slow response to command time is not consistent. The majority of all my files are x-reffed. I have all my title blocks as overlays and all other x-refs as attached. The cache time when switching back and forth from model and paper is prolonged terribly too. This happens in multiple drawings but not all, all of the time. Opening block editor is a definite problem as is maneuvering around in the layers dialogue box. Any clicking in the layes dialogue box in EVERY drawing is very prolonged. Thanks for your time

[rkmcswain]

You can watch file and registry activity in real time using this (http://cadpanacea.com/wp/?p=504). So when it's frozen, you may be able to see why it's pausing.

[Ed Jobe]

Something else you can check into is virus scanners. I had Norton and sometimes it would quit working properly and everything would be slow. Try turning it off and see if things speed up. On the other hand, make sure you've done a complete scan and nothing has been found. Also, make sure it isn't scheduling a scan during work hours.

[Tom Beauford]

Have you attempted to rule out the network by by testing a drawing whose only references are on your local drive?
What size drawings and xrefs are you working with?
What else is referenced as far as GIS or images?
Are you doing 3D work?

[lmessal738905]

Check out the release from Autodesk. This increased our file performance by incredible amounts. Seriously, we were dead in the water practically and we replaced the AeccdbNetwork.dbx file (follow the link) and our files were opening in ten seconds instead of 7 minutes and our performance within cad was considerably better! Good luck.

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Civil-3D-Performance-degradation.html

[jpaulsen]

You mentioned the layer dialog a few times. Have you tried to set LAYERDLGMODE to 0?

[rkmcswain]

Check out the release from Autodesk. This increased our file performance by incredible amounts. Seriously, we were dead in the water practically and we replaced the AeccdbNetwork.dbx file (follow the link) and our files were opening in ten seconds instead of 7 minutes and our performance within cad was considerably better! Good luck.

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Civil-3D-Performance-degradation.html

The fix you reference above is only for Civil 3D, and the OP said they are running vanilla AutoCAD.

[NDPlantDesign]

Ed,
I haven't ben able to find the common denominator yet. It's driving me crazy. The slow response to command time is not consistent. The majority of all my files are x-reffed. I have all my title blocks as overlays and all other x-refs as attached. The cache time when switching back and forth from model and paper is prolonged terribly too. This happens in multiple drawings but not all, all of the time. Opening block editor is a definite problem as is maneuvering around in the layers dialogue box. Any clicking in the layes dialogue box in EVERY drawing is very prolonged. Thanks for your time

In Options, on the System tab, try changing the Layout Regen Options to help the caching time when switching between layouts and paper space.

If you have one or more external references that don't need to be showing at all times, unload them. I do this often with images, but also for drawings that are only added for reference and don't need to plot. Also try purging the layers that you don't need, so there are fewer layers to load every time you try to open the layers dialog. It may also be helpful to purge all of the drawings you have xrefed to cut down on the number of layers as well.

[joe.franco420344]

Your files might be bloated. Try purging your files with this lisp routine I've put together;




;------------------------------------------------------------------
; PURGE, AUDIT, NLFK2, SCALELISTEDIT, DGN LINETYPES & LAYERSTATE
;------------------------------------------------------------------
(defun c:CLEAN()
(COMMAND "-SCALELISTEDIT" "R" "Y" "E")
(COMMAND "-PURGE" "A" "" "N" "-PURGE" "A" "" "N" "-PURGE" "R" "" "N")

;----- Remove Named Layer Filter ----------------
(vl-Load-Com)
(vl-Catch-All-Apply
'(lambda ()
(vla-Remove (vla-GetExtensionDictionary
(vla-Get-Layers
(vla-Get-ActiveDocument
(vlax-Get-Acad-Object))))
"ACAD_LAYERFILTERS")))
(princ "\nAll layer filters have been deleted.")
(princ)
;------------------------------------------------

;----- Delete all Layer States ------------------
(foreach state (layerstate-getnames)
(layerstate-delete state)
)
;------------------------------------------------

;--- Reset Lineweight in Layers to "Default" ----

(command "-layer" "LW" "default" "*" "")

;------------------------------------------------

;----- Clean dgn bloat --------------------------

(if (dictremove (namedobjdict) "acad_dgnlinestylecomp")
(progn
(princ
"\nClean DGN bloat complete. Please check your file for any errors. A purge is recommended."
)
)
(princ
"\nacad_dgnlinestylecomp not found. This file will not benefit from cleandgnbloat."
)
)
(princ)

;------------------------------------------------

(COMMAND "AUDIT" "Y")
(COMMAND "-PURGE" "A" "" "N")

) ;end of clean



It's several lisp routines in one
It has worked wonders for me, reducing file sizes from 4Mb to 100Kb.
Also I use classic Layer Property Manager, much quicker.
You can download this file "AjilalVijayanDrawingPurge.msi" from Autodesk App Store. This would clean all selected DWG's at once.
Hope this helps