During the time that it is spiked out of course no other jobs can work with it until this process gets killed or dies off naturally. I've been trying to investigate to find out what is causing this but haven't seen a concrete answer.
Any ideas/thoughts from the community on this?
Did you solve your problem ? I think I have same issues : InDesign server (CS5.5 on mac) stuck at 100% of CPU after the job being done.
Did you use multi instance or single ?
Yes we solved it. We had a background process in our app that was trying to send over a thumbnail generation script. This would peg the INDS server for up to 15 minutes of just doing nothing. You would see the script come across but nothing would return so it would hose. Ended up fixing the error in our application and INDS has been working like a dream.
When we were running this we only were on a single-instance. We've now migrated to a multi-instance and throughput seems to be a lot faster now.