General infrastructure and database performance analysis - SmartPlant Foundation - IM Update 46 - Help - Hexagon

SmartPlant Foundation Help

Language
English
Product
SmartPlant Foundation
Search by Category
Help
SmartPlant Foundation / SDx Version
10
SmartPlant Markup Plus Version
10.0 (2019)
Smart Review Version
2020 (15.0)

If configuration changes do not improve performance, further analysis is required to determine the cause of the problem. Infrastructure and database performance can have a major impact on general performance.

  • Perform representative benchmark query tests as suggested so that changes to the system can be properly evaluated.

  • Perform tests on simple data for comparison with standard performance tests. Using a find method to return all schema interfaces starting ISPF* is an example of a simple test. The out-of-the-box database returns approximately 450 of more than 2100 interfaces and takes one or two seconds to display the results. A search for all properties (approximately 3600) should take about 5 seconds.

  • Performance tracing is not very helpful for analyzing queries, as it is very granular and verbose. It is primarily useful when conducting detailed analysis of the problem.

    • Turn off performance tracing and turn on SQL tracing, which helps identify where there are large numbers of objects being returned, for example, building a form and returning 1000 objects or items to relate. The trace does not provide the amount of time elapsed, only the actual start and end times of each SQL call.

    • Use additional database profiling documentation to import this data into a spreadsheet and run a macro that calculates the differences and presents the times for each SQL call. This information can help determine if the problem is with the database (such as tuning), poorly structured SQL (a TR on the product), or system configuration.

  • Use the performance benchmark tool to better determine the amount of time taken to perform the query and serialize its results.