Configure Performance Monitor Memory Trace for troubleshooting possible memory issues

Problem: 

To find a memory leak requires a detailed look to the system's RAM usage. This can be accomplished in Windows by using the Performance Monitor.

Answer: 

AutoStore Process Designer must be open while the Performance Monitor is being set up.

1. Press Windows+R to open the Run dialog;
2. Enter "perfmon" and click OK.
3. Open “Data Collector Set”\UserDefined\, right click and press “New -> Data Collector Set” .
4. Enter a name and choose “Create manually (Advanced) and press next.
5. In the “Create data Logs” tick “Performance Counter and press next.
6. Click add and select the following counters.

• LogicalDisk\Free Megabytes
• Process\% Processor Time
• Process\ID Process (Total)
• HandleCount  
  • Select the below Instances of counter 
    • ASCompHost*
    • Batch
    • OCRService
    • OCRServer
• WorkingSet
  • Select the below Instances of counter 
    • ASCompHost
    • Batch
    • OCRService
    • OCRServer
• WorkingSetPrivate
  • Select the below Instances of counter 
    • ASCompHost
    • Batch
    • OCRService
    • OCRServer
• PrivateBytes
  • Select the below Instances of counter 
    • ASCompHost
    • Batch
    • OCRService
    • OCRServer

 

Please note: that the above configuration will work only if running a single batch service and only one ASCompHost running at a time. Performance monitor adds a counter to the process name if there are multiple ones present at the same time, i.e. “chrome”, “chrome #1”, etc. If there is more than one workflow that has an isolated component(s) then there’s a chance for multiple ASCompHost processes is present at the same time. In this case a preparation of the Performance Monitor data collector to collect information from all instances is required, not just one.

For example;

• Batch (multiple instances are possible only if multiple batches are started, either as a service or from command line)
• ASCompHost (multiple instances are possible if more than one component is isolated)
• OCRService (only a single instance is expected)
• OCRServer (multiple instances are present if multiple OCR licenses are activated of more than one OPSDK related component is present in the configuration; usually not more than 4)

The setup should look like below

Please click HERE for a video on the steps defined above.

 

 

Applies to:  

Product	Version
AutoStore	7.x
AutoStore	8.x
ControlSuite	1.x