Developer forum

Forum » Development » Peformance CPU load on OnPreRequestHandlerExecute

Peformance CPU load on OnPreRequestHandlerExecute

Martijn van Tongeren
Reply

Hi,

We discover a problem with a massive CPU usage. When the site is loaded we start a stress test. The cpu is growing and growing till 100%. We use ants profiler to monitoring the cpu we see that  Dynamicweb.Frontend.GlobalAsaxHandler.Application_OnPreRequestHandlerExecute method stall the process and cpu is going sky high (see screenshot). We using version 8.6.4.1 someone any suggestions??

Br, Martijn

cpuload.jpg

Replies

 
Morten Bengtson
Reply

Looks like some of your requests contain data that is considered malicious by DW. The IP address might be banned and then DW will deny any further requests from that IP.

Have a look at the file /Files/System/_BannedIps.txt - Does it contain any IP addresses?

You can try to change the security settings and see if it makes any difference.

 
Nicolai Høeg Pedersen
Reply

I think Morten is right. DW sleeps the thread 4 seconds before giving a 403.1 response code to banned IPs

 
Martijn van Tongeren
Reply

Hi Morten, 

Thanks for the reply. As you suggest i disable the security setting, after disable it, it doesn't genarate a _BannedIps.txt file. But still I have the same issue, cpu load grows to 100% and this didn't stop, see also screenshot. It looks like  Dynamicweb.Frontend.GlobalAsaxHandler.Application_OnPreRequestHandlerExecute(sender, e) is the issue. 

Do someone have any suggestions?

Thanks!

cpuload1.jpg
 
Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Reply

Did you drill into the 17 hidden child methods that generate the spike in CPU? That might shed some light.

Imar

 
Martijn van Tongeren
Reply

unfortunately it's not possible to view this code. I tried to download the debug symbols of version 8.6.4.1, but these are not available. I will try to update to the latest 8.6 version....

 
Martijn van Tongeren
Reply

I update to version from 8.6.1.4 to 8.6.1.10, so far i can see now this solve the issue. I read the releae notes and see change according this issue...

 

You must be logged in to post in the forum