Question

FSM w3wp worker process is not releasing the memory even no one is accessing the application

  • 21 October 2020
  • 3 replies
  • 217 views

Userlevel 4
Badge +8

FSM w3wp worker process is not releasing the memory even no one is accessing the application. W3wp worker process is consuming a lot of cpu  that is downgrading the performance of the FSM application. But even no one is accessing the application and no back ground job is running also the W3wp worker process CPU if not reducing. Only after recycling the Application pool the worker process cpu is reduced to low and we are able to access the application.


3 replies

Userlevel 7
Badge +24

Hi @TatKhandM,

It sounds like there was some large process that was stuck. If you extract a dump file of the w3w process when this occurs before recycling and log a case with support they may be able to analyse the file to determine what process specifically was stalling. 

Were any large processes started prior to the drop in performance? Perhaps a large data import or update either manually or from an integration? These can persist after the initiating user has logged out of the application.

It would be good to check the run logs in the system and see if any have errored or still show as processing that have a start time from around when the performance dip occurred.

 

Kind regards,

Lee Pinchbeck

Userlevel 4
Badge +12

@Lee Pinchbeck I have a customer that is experiencing the same issue where w3wp.exe is consuming high CPU during Invoicing. Could you explain what the steps are involved in order to collect this dump that you speak of? Also will it have an impact during invoicing? 

Userlevel 7
Badge +24

Hi @Ann Degroat,

You would need to open up task manager on the app server, highlight the process for w3wp.exe that is consuming the CPU and then right click. You should see an option to create a dump file. It can take some time to generate.

Usually you would do this though when you are seeing high consumption but do not know the cause. It would seem like you know the cause is invoicing in your case?

Kind regards,

Lee Pinchbeck

Reply