PDA

View Full Version : AutoCAD LT 2015+ Z230 tower work station slow drawing operation



max_kool
2016-05-05, 05:35 AM
Hello All,
We are having AutoCADLT 2015 and AutoCAD LT 2016 (64bit) installed on Z230 HP work stations.
machine config - Windows 7 (64bit) + Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz + 16Gb RAM + 4Gb Nvidia Graphic Card K2200.
Network - 1Ghz, CAT6 cables
When we work on some of the files with xref or lot of blocks in it, then AutoCAD takes lot of time to respond. Sometimes it just crashes up. Drawing file size - 10-15Mb.
We tried cleaning / deleting temp files, the C:\ is having lot of empty space. Drawings are accessed over network. No other programs are running expect for Excel along with it.
Number of drawings opened at one go is 4 maximum.
Any idea where we have to look for problem ?

Thanks in advance

Rahul

JGA_o1
2016-05-09, 10:18 AM
We have a similar spec. of PC, so I know that it'll not be the hardware.
Are the Xrefs settings set to copy to the PC (XLOADCTL set to 2)? If not, you will be accessing the network for the Xref during the drawing session.
The file sizes look bloated, to be honest. I'd purge all the files & run audit to ensure that there are no underlying problems in the drawings themselves.
Check what palletes are open - the layer pallete is a traditional slow point, as it updates to reflect what viewport you are working in.
Finally, check with your IT guys to ensure their security settings & network speeds aren't a bottle neck for large CAD files.
Best of luck. If you find a solution, can you please post it? Thanks.

rkmcswain
2016-05-09, 11:15 AM
Make sure your %temp% folder is fairly clean.
If it contains tens of thousands of files/folders - time for a clean.

Are these 10-15MB files really supposed to be this size?
Make sure they are not polluted with one of more of the big three (Scale list entries, Regapps, DGN linetype bloat)

Other than that- start eliminating items one at time.
For example, move the files to a local drive and unplug the network cable... any faster? If not, then you know it's not a network issue.