Performance analysis for Produmex Scan

During daily usage you may experience overall system slowness from Produmex Scan application. There can be many reasons for slower performance and there are a couple of checks that can be done before opening a support ticket.

The following template can be used to gather information and provide attach it to any support ticket related to performance issue. 
With your cooperation gathering and checking these details will speed up the issue analysis process.

Check recommendations and server role split up

http://wiki.produmex.name/doku.php?id=implementation:general:hardwarerequirementsserver#produmex_scan_operator

Kill time setting of Service Broker
 

http://wiki.produmex.name/doku.php?id=implementation:scan:service_manager

Recommendations for MS SQL server setup

http://wiki.produmex.name/doku.php?id=implementation:general:hardwarerequirementsserver#mssql_server_configuration

Network configuration and coverage

You need to ensure the network is stable and the coverage is sufficient in all warehouse areas.
The recommended connection between each server and the database server should be a link aggregation of 4 gigabit ethernet connections.

Run diagnostic tests and verify results

http://wiki.produmex.name/doku.php?id=implementation:scan:client_configuration#diagnostics_tab

Diagnostics should be run on the server where the Service Broker service is running, you can use the windows emulator for this.

Then you need to run the Diagnostics on the physical handhelds used around the warehouse on the local network.

You can now compare the values for these diagnostic results:

*results were measured on a local laptop, so you might have better values running the tests on a proper server configuration.

If you see that the results on the Local network are higher than the Service Broker server, that means you should improve your local network.

 

If you see that the results on the Local network for T03, T04 tests are significantly higher , that means you should investigate your database server performance, or the network connection between the service broker and database server.

Check the processes without any customization

You need to manually rename and temporarily disable your customizations and check your process. Then with one by one enable your customizations to detect which might cause the issue. Then you need to fine tune, or rewrite your customization queries.

Use MS SQL Tuning advisor to get optimization recommendations
 

You can follow the steps in the article based on WMS, but it can be also used for Scan as well.

https://support.boyum-it.com/hc/en-us/articles/14826172784925-How-to-use-MS-SQL-Database-Engine-Tuning-advisor-for-WMS-related-performance-investigation

Turn on DEBUG log to gather every steps while you are testing and reproducing the issue

https://support.boyum-it.com/hc/en-us/articles/6326397921821-How-To-Set-Up-Log-Level-In-Produmex-Scan

Check your Cloud environment setup with the help of Cloud Provider administrators

In case you are running on a hosted environment it is always needed to include the cloud provider's admin team. They can check resources and provide help on investigation.

• PERFORMANCE_ANALYSIS_PRODUMEX_SCAN.xlsx10 KB