Summary

Actions in your Performer Suite itself trigger database calls. If the latency to your database is very high, it leads to performance losses even though the database server itself is fast.
 Such latencies can occur due to complex network architectures, database-location is in another country, security checks, slower machines like a Virtual machine (VM) or simply missing bandwidth.

What can we do to improve the speed

Short version

Bringing the database closer to the Performer Suite will improve performance.

Detailed

1. Keep the latency to your database as low as possible:
   1. The installation location for the Performer Suite is important. Avoid installing the Performer Suite on a slow network drive.
   2. If you are using CITRIX or Virtual machines: Please ask your Network Administrator for assistance on how to reduce latency to your database or even improve the speed of the database.
   3. If your database is in another country, try using a database that is rather locally in-house.
2. bluetelligence: Describe unusually slow processes within the Performer Suite in detail so that we can recreate the issue and try to fine-tune the database calls → Service Desk

Database Speed Test

You can run a speed test and compare it to our results in the EXCEL sheet below:
20200722_Speed_Test_Comparison_pubv2.xlsx

 If your READING values differ too much into being way longer, the issue could be your network latency or network security checks, e.g. Firewall.

SQL Server (centralized) vs. Oracle (centralized)

Further information

• https://blog.packet-foo.com/2014/09/how-millisecond-delays-may-kill-database-performance
• https://solutioncenter.apexsql.com/how-to-monitor-and-detect-sql-server-round-trip-performance-issues-using-custom-designed-metrics