Tuesday, 22 May 2012

ClientDependencyLoader takes 100% of CPU

One of my clients had serious problem with DotNetNuke 6.1.4 Pro. His site had small number of visitors at start, but after some advertisement, number of visitors jumped to the 30,000 uniq visitors per day. Site was under the good dedicated server (2*Xeon and 16 Gb RAM), so client did not expect any problems with performance. But one day CPU has taken 100%. Site was very hard to open. It was real problem. We had to make deep digging with JetBrain tools and at the end of end we found problem. 90% of each thread calls ClientDependencyLoader from the ClientDependency.Core! It was a source of problem. To turn it off we had to change the web.config:

<compilation debug="false" strict="false">

to this one:

<compilation debug="true" strict="false">

I know, this is not good trick, but at least CPU back to the normal 25-35%.

No comments:

Post a Comment

Note: only a member of this blog may post a comment.