Hi @Narsing Rao what are the specs of your Server and how many Users working with your environment? If this is a DEV environment, you may want to recycle the FSM Server App Pool for an immediate remedy. However, if the memory consumption is always high on your Server you may need to investigate if this is due to some transactions or not enough memory allocated to the Server.

Best regards
Roman

Hi @roklde,

Thanks for your support.

As an immediate remedy we do the App pool refresh or restarting the IIS, but these tasks were not bringing the memory consumption down in server. Still, we are able to see in server log same message.

Message: PerformanceMonitor memory threshold to abort threads = 19326950400 bytes. (75% from machine).

Thanks & regards,

Narsing

Can you please answer my other questions? Are you running the FSM Server on the same host as the Database? Please also confirm if the IIS Worker Process for the FSM Server conusumes that amount of memory or if a different application is consuming it.

Best regards
Roman

We have dedicated servers for Application and Database.

In Application server, the task manager is hanged up so when we open it, we can see the CPU and Memory utilization in same percentage whole time until we reopen it.

And the IIS worker process CPU consumption is under 5% to 10% and Memory usage was 938 MB.

Thanks & regards,

Narsing

So, it’s not FSM causing the high Server utilization? Identify what other program is causing it and try to find out why.

Best regards
Roman