On premise CRM is slow

Hi Community,

 

Any idea what might be the problem to why currently our on premise CRM is slow. Below is the screenshot of network log while navigating through section and edit pages.

 

Other  details:



1. It is using oracle DB

2. We monitored the application and db server while navigating through section and edit pages and the CPU usage is just hitting only 30%.

Like 1

Like

2 comments

Interesting, having the same issue with a client, on-prem with oracle DB

Hello Fulgen, Damien. 



Please make sure that your server machines fit  the requirements. 

You can check it here



On top of that, please analyze following information:



For both Appserver and DatabaseServer

  1. Analytics and monitoring results in graphs displaying the data for the problematic period:
  • % CPU load  
  • % RAM load
  • Disk transfers / sec (IOPS)
  • Disk Read / Write Latency
  1. Application logs (default direcotry C:\Windows\Temp\BPMonline\Site_<website number>\)

Note: how to find the website number?

  1. IIS logs for the period when issue occurred (C:\inetpub\logs\LogFiles\W3SVC<website number>)
  2. Windows logs for the period when issue occurred
  3. Website diagnostic information from procDumpLite utility

IMPORTANT: If you are using balancer or any other infrastructure to prevent fall-overs, it is necessary to provide the diagnostic data of all the nodes.

 

1.     Extended Events (for MS SQL Server) or AWR Report (for Oracle) for the problematic period Note: How to set up Extended Events https://docs.microsoft.com/en-us/sql/relational-databases/extended-events/quick-start-extended-events-in-sql-server?view=sql-server-2017

2.       MS SQL has the option to track the current server activity. Below are the scripts that will display the server activity for the problematic period.

 

Actions to perform when the issue persists

1.     Launch procDumpLite.exe utility in Web Server

procDumpLite.exe site=your_site_name collect=activeRequests,stackFrames,perfViewProfile,memoryInfo

2.     Launch the stored procedures to collect the diagnostic information in Database Server.

exec sp_collectBlockedProcess

exec sp_collectActiveProcess

Note: It is necessary to launch the following stored procedures in separate session and make sure they are running at the same time.

3.     Export the recent records from the ActiveProcess and BlockedProcess to Excel sheet.

select * from ActiveProcess where [CollectedTimeStamp] > cast(getdate() as date)

select * from BlockedProcess where [CollectedTimeStamp] > cast(getdate() as date)

Export the Extended Events (MS SQL) or AWR Report (Oracle)



Analyze received information. 

If after initial analysis you're still unable to find the reason of the slowness, please contact us at support@creatio.com and provide the information you've gathered. 



Best Regards,

Yurii.

Show all comments