[Report] the blog garden program encountered another problem last night.

First, I apologize again! Thank you for your understanding!
I came back at nine o'clock last night and found that there was an old problem in the blog Park. The access speed was very slow and almost inaccessible. The "server application unavailable" error often occurred, the source of inspiration reflects the problem that occurs more than six o'clock in the evening. Since Program After the upgrade, this problem has been plagued by the blog Park. This problem has occasionally occurred before, but is more frequent after upgrade.
Yesterday morning, I migrated the program from the server provided by csdn to the original server to find out the real cause of the problem. After the migration, the system runs normally during the day yesterday.
When a problem occurs, the server's CPU usage remains at 100%. The SQL Server and Asp.net processes occupy the CPU. I used the SQL event probe for tracking and found that blog_genericgetentries_10 and blog_genericgetpagedentries_10 stored procedures were executed for a long time, sometimes 5 or 6 seconds. This is the most frequently used stored procedure of the blog garden program, after the program is upgraded, you can call these two stored procedures. The homepage and each website category call these two stored procedures. In the SQL event probe, the occasional audit logout takes a longer execution time, which takes dozens of seconds or even minutes. What is audit logout? What causes audit logout? What is the relationship between audit logout and. Net sqlclient data provider? In the SQL event probe, the applicationname of the audit logout event is. Net sqlclient data provider. Please advise.
I carefully analyzed that blog_genericgetentries_10 and blog_genericgetpagedentries_10, blog_genericgetpagedentries_10 are a paging stored procedure, and blog_genericgetentryids_10 is called. The only suspected problem is that with (nolock) is used for each query statement in the two stored procedures (blog_genericgetentries_10 and blog_genericgetpagedentries_10 ). I don't know what to use with (nolock) in. Text )? I guess it may be that with (nolock) caused the SQL Server deadlock. Now I have removed the with (nolock) in the query statement to see if the problem still exists?
I hope you will give suggestions, analyze the causes of the problem, and provide some solutions.
Some related information I found online Article :
Http://forums.aspfree.com/t22127/s.html
Http://www.devmanclub.com/showpost.aspx? Postid = 2432 #2432