Data modifications view
The Data modifications view covers all applications that modify the core data of the platform (contacts, portfolios, customers, transactions, trade orders, and so on).
Except for the Database latency, all charts show the values split by:
Data type (portfolio, transaction, trade order, and so on).
Operation type (create/update/delete portfolio, security, and so on). One data operation means an addition/modification/deletion of a single data row in FA. For example, creating a new transaction in FA results in two operations: a transaction creation operation, and a separate transactionVO creation operation.
Note
As the chart lines are quite narrow, values might not show up until you zoom in a bit, especially on a bigger scale.
- Average data change latency per data type
The average time (in milliseconds) per data operation, broken down by data type. Spikes on this chart may indicate a (temporary) performance bottleneck.
- Average data change latency per data type and operation type
Same as above, broken down by data type and operation type.
- Time spent on data operations
Total amount of time spent on various data operations during a given time window (1-2 minutes), broken down per data type. Spikes on this chart indicate that extensive data modification took place at a given point in time; it doesn't automatically indicate slowness.
- Time spent on data operations per operation type
Same as above, broken down by data type.
- Data changes per minute
The number of objects created/modified/deleted during a given 1-minute time window. Due to technical reasons, the numbers might not be fully accurate, especially with smaller modification counts, but close to it. Spikes on this chart aren’t directly indicative of the performance, they indicate extensive data modification taking place.
- Data changes per minute per operation type
Same as above, broken down by operation type.
- Database latency
The database response time. The values on the chart should normally stay under 1 millisecond. Values that permanently exceed this limit indicate a potential problem in the technical setup. Spikes in these values may indicate performance problems.