CPU Spiking

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
6 years ago
We have been fighting issues with our nopcommerce 3.7 site the last week or so with our CPU spiking up and we have increased the CPU allotment and still having issues randomly. We have uninstalled plugins and even replaced plugins thinking it was that. Does anyone know of a way we can figure out what is causing the spikes?
6 years ago
Are you absolutely certain that it's the w3wp.exe process specific to your site that's spiking?

You can check it by right-clicking the IIS Worker Process process in Task Manager, then choose Details.
The "username" column indicates the application pool and will be your clue as to which site it is that's spiking.

You could try enabling the mini-profiler to see what elements are taking the longest to load.
Go to admin >> Configuration >> Settings >> All Settings (advanced) >> find this setting:
storeinformationsettings.displayminiprofilerinpublicstore

Change it to true and update it. Now you will have a small overlay in your upper left corner of the screen on your pages. Click around in that and see if you can learn anything.

Also, Chrome's web developer tools extension has a Performance tab that allows you to start recording a profile of the Javascript drain on your CPU for your pages. You just click the record button, refresh a page, and look at the numbers. This might also give you a clue.
6 years ago
It is indeed the w3p and its using over 10gb of memory and keeps spiking like crazy, we are noticing we are getting over 150k customers created in our database a day and we had 15 million before we cleaned them up.

Do you think its these customers being added? We are seeing about 5-10 created per second in the customers database. How do we handle it?
6 years ago
That happened to us as well a couple of years ago.
I deleted a million records, but the damage was already done. Our database size bloated up to 140gb..very frustrating.

The best thing you can do is to get this plugin. You must spend a small amount of time learning the IP's and/or IP range of your attackers..or even just countries of the attackers, and add them to this plugin list. They will be denied access to your site after that.

This was my initial posted problem:
https://www.nopcommerce.com/boards/t/32088/thousands-of-empty-customer-records-created-every-day.aspx#137834

very similar, huh?

In the same forum topic, I said this:
https://www.nopcommerce.com/boards/t/32088/thousands-of-empty-customer-records-created-every-day.aspx?p=3#165282
6 years ago
embryo wrote:
That happened to us as well a couple of years ago.
I deleted a million records, but the damage was already done. Our database size bloated up to 140gb..very frustrating.

The best thing you can do is to get this plugin. You must spend a small amount of time learning the IP's and/or IP range of your attackers..or even just countries of the attackers, and add them to this plugin list. They will be denied access to your site after that.

This was my initial posted problem:
https://www.nopcommerce.com/boards/t/32088/thousands-of-empty-customer-records-created-every-day.aspx#137834

very similar, huh?

In the same forum topic, I said this:
https://www.nopcommerce.com/boards/t/32088/thousands-of-empty-customer-records-created-every-day.aspx?p=3#165282


really appreciate the responses embryo, we are not really getting requests from people we dont want but its all search engine bots. For example here is a list of the accounts being created by ip address, almost all are googlebot, amazon and bing bot. How do I get those into the isystem account so it doesnt keep creating them? I want them to crawl our site just not keep creating customers account
6 years ago
I see...well...the last couple of pages on that same forum topic I linked to seem to be where you need to be looking....good luck man!
6 years ago
I see how to block ip addresses which I dont want to, but nobody clarifies how to get the good bots to not create accounts?
6 years ago
In older versions, I know this is working perfectly...maybe some bots changed their "profile" and now nop just doesn't recognize when it is Google or Bing anymore???
6 years ago
Ok update on this.. we are still having issues not as crazy as before but we have trouble a couple times a day. We get around 100 active users via google analytics during peak days like today.

Our W3wp.exe file was running 4GB in the task manager and so I changed a few settings and curious everyone's thoughts?

We changed the following this morning:

QueueLength from 1000 to 2000
Start Mode from On Demand to AlwaysRunning
Maximum Worker Processes from 1 to 3 (This is causing customers to get 3 emails from nop like order receipts, order shipped.etc)

This is what we are seeing in the event viewer before these changes..."Unable to read Server Queue performance data from the Server service. The first four bytes (DWORD) of the Data section contains the status code, the second four bytes contains the IOSB.Status and the next four bytes contains the IOSB.Information."


Thoughts?
http://imgur.com/a/wJCdO
6 years ago
Ok I found this awesome article here https://stackify.com/w3wp-high-cpu-usage/ and found out how to turn on requests to see whats running on the app pools. We had an instance this morning where our CPU is spiking and its all from hundreds of requests to our /filterSearch? page all backed up. Something is trying to search upc's and product names of products we dont carry. The ip addresses are all random so it looks like someone is using a proxy to do it. We disabled full text search in the nopadmin and the cpu is not spiking as bad anymore but now our memory is climbed to 8mb making our site really sluggish.

Does anyone know how to stop these?

We also notice in all of there requests its adv=true&sid=true meaning its searching in the description for these and do youll know how to stop it from doing that so it doesnt take up more memory searching through the descriptions?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.