Hope all is going well. It's been a while, so I don't remember exactly what we did to resolve this, if anything. To be honest, we may have just stuck it out until an AGS upgrade, but our issue was of course on development which allowed us that flexibility. There were are few issues we had going on around this time, so here are some things we did around that time to resolve issues ... maybe one of them will be useful?
- Created a new, identical map service and used that in place of the one with the issue
- Restarted AGS and then the server itself (I know this is an obvious one, but it's amazing how many times it has resolved our issues.)
- Republished the service, removing one layer at a time, to determine if one layer was the culprit or if it was an issue with the service/AGS.
- Republished the service pointing to a copy of the data. Copy of the data wasn't a copy/paste or import, but a clean feature class, import schema, then append.
Also I'll double down on David's suggestion of Anti-Virus software. I know that was a major issue for us at one time in a previous AGS release. Simple rule change cleared it all out.
Sorry I couldn't be of more help!
Thanks again Shaun and David for the replies and help! I have a few updates to pass along just in case anyone suffers this CPU behavior going forward. It looks like there are a myriad of issues causing our problems for our production server. The steps we have taken and the issues that have been identified:
Hope this helps guys- if we figure out anything else I'll update this. Thanks again for the info and assistance!