Our server recently got tied up running backups, so all performance suffered for a morning, but it revealed some of Civil 3D's behavior that may otherwise go unnoticed. Here's relevant details:
Many, many common functions of even vanilla autocad were unreasonably slow. Why should there be a 20 second delay after clicking a hatch to grip edit? Why should there be a delay after editing a feature line (no auto rebuild)? I understand the lag with rebuilding the surface, but not the simple things. It was my understanding that AutoCAD had a system where all drawing data is been copied locally to work on, and saves go back over the network. It seems like Civil3D / AutoCAD generates a ton of unneccesary network traffic for many things which should be able to happen strictly locally. Am I missing out on a setting somewhere?
Typically when I see selection delays and weird lags it's related to either a driver issue or something to do with your video/display settings.
Steve (good name!)
thanks for the reply. I've pretty much work through all my issues with drivers/video a while ago and my only complaint about normal operation has to do with the lag cause by having the properties window open. I'm hoping to find out if anyone else has seen behavior like this, or to get AutoDesk's attention to look into why they seem to be generating so much network activity. In this case, I know the system (network) was slow because the server was overloaded. My problem is, with the way I have it set up, why should our slow server affect the program performance so drastically in operations outside of open & save?
I have a Network Activity Indicator app running that shows the blinking monitors (like windows xp) with network traffic. When there's a delay with Civil 3D, i see an outgoing blip, a delay, and as soon as the incoming blip is done, Civil 3D comes back to life. That little app really makes me aware are how much traffic is being generated. Funny thing is, there've been times when I've worked at home, with no network connection, and have much better performance from Civil 3D than at the office.
I have those issues also. Keeping toolspace closed helps with certain issues. Same with SSM.
I've done some testing with 2013, and it works much better than 2012. A lot of issues just don't exist in 2013 that are just maddening in 2012. Problem is, we haven't put 2013 into production yet, and while it takes care of most of the issues I have with 2012, it appears to have a whole new load of new issues all it's own.
We are also experience the same issue where either Civil 3D, ADT, or MEP 2012 or 2013 seem slow over our network. I'm hoping I can get other people to run a test to see if other users are having this problem but before I do I will explain our company and network and what I have done with the network and what I have found out.
Sorry for the long reply but I think this problem is important and is affecting a lot of Autocad users.
For starters people either complain on how long it takes to open, save, plot, work on a hatch, the first time you launch Mtext, and especially using Sheet Set Manager (SSM). So I have been doing a lot of research and I have concluded that if you are sharing any standards on a network on a shared drive is when all these problems occur. If you use Autocad just out of the box and locally everything works fine.
So I have been doing a lot of research and have spent a lot of time and money on our network to solve this problem and it's still not completely solved. So in my opinion the problem is with the Autocad code and working across any type of network.
Our company is an Architectural, Engineering, Environmental, and Surveying with 8 offices.
All 8 offices are connected on a Wide Area Network, 6 have 20mb, 1 has 40mb, and our main office has a 60mb WAN connection. Our main office is where we store all of our companys files and Autocad standards so all 7 offices are working back to our main office. I would say on average our main office pipeline is using only about 30mb through out the day. All of our servers are using Microsoft Server 2008 R2, and all of our workstations are using Windows 7 Pro 64bit with about 16gb of ram.
When I started looking into this problem I thought it was our network at one of our offices that was at 20mb so I upgraged and bumbed it up to 40mb and this office has 40 employees and I would say 20 are using Autocad.
That did help but not what we were expecting. Before I forget our local users at our main office where also complaining about how sometimes Autocad is slow, so it's not just our users outside of our main office where the main file server is. So doing more research I have seen discussions about turning stuff off in Autocad and we did all of that and that improved it a little bit but again not to our expectations. For example I told people to close all palettes, tell SSM not to sync, turn off digital signature, and upgraded network and video drivers, so pretty much I did everything possible I could with Autocad and the workstation and still we are not getting the performance that we expect.
I then found these two programs that would capture our network and workstation traffice and they are:
Process Monitor http://technet.microsoft.com/en-us/sysinternals/bb
Wireshark http://www.wireshark.org/ I used this program to capture all network traffic.
This where I need your help, if someone at least could download the Process Monitor and capture traffic on the workstation and see if you get the same results as I do. You aren't going to believe this if I read the data correctly.
Basically Autocad is looking for about 30-50 files and it's searching in about 30-40 different folders looking for it and basically can't find it. For example it might be looking for a file called gdi11.hdi and it will look for it in for it all over on the workstation and if you opened a file on the network then it also looks for it and if you have any custom file search paths in your Autocad profile it will also look in those folders. So if you can imagine everytime you open, save, print, switch between model and paperspace it's contastanly looking for files in all the wrong folders so no wonder it takes Autocad so long to just launch or to open, save, print, etc... it's wasting a lot of time looking for files and wasting our bandwidth.
If you decide to use Process Monitor to run this test and see for yourself I recommend using a filter so that you can just see the acad.exe process and what files it can't find.
In Process Monitor go to Filter / Filter and you will be adding three seperate filters.
1.Process name is = acad.exe
2.Operation is = CreateFile
3.Result is = name not found
What you can also do is start and stop and clear the events just to see what Autocad does, for example capture what Autocad looks for starting up, stop it and then clear it while leaving Autocad open, then start the capture again with a clean slate and now open a file, and do the same thing for printing, switching between model space and paperspace, etc... and you will be amazed.
So I would be curious if others are seeing that the acad.exe process is wasting a lot of time looking for files in the wrong places causing Autocad to act slow on certain operations. I'm currently working with our reseller who is working with Autodesk on this right now and I think if I can more proof and help from the outside I think we might have a better chance of Autodesk listening and fixing the problem.
This is a top contribution, thanks. Seems AutoCAD is getting more and more busy with itself, and there is less and less processor time left for the user.
I'm running 45 survey crews on three LNG construction sites, and apart from the networking issues we have the additional company security further crippling the users. I have my own personal notebook with a local install of AutoCAD Civil3D, connected to nothing and using a USB-stick network to transfer files when needed. It is so much faster than the company CAD machines, and does not suffer from lags. The company ones keep going into short (2-10 second) "hang ups" every couple of minutes, as AutoCAD wrestles with network, firewalls and security I think, very frustrating and needless.Press F1 and it takes 30-50 secs before the help comes up (although the "access online content" check-box is unchecked). It's quicker to Google the problem.
Just watching AutoCAD start up, partial menus get displayed, taken away, redisplayed, the screen gets reorganized about a dozen times before the eventually system settles down, pays attention to the user and the keyboard and mouse accept input. Messy.