How to find which analysis consumes more memory while troubleshooting Spotfire Web Player's high memory utilization
Article ID: KB0070231
Updated On:
| Products | Versions |
|---|---|
| Spotfire Web Player | 7.5 and higher |
Description
There is no way to find the exact amount of memory utilized by an analysis which is opened on the Spotfire Web Player. This is because all of the memory is handled on a block level. The data engine is not aware of 'analyses' (i.e which block belongs to which analysis), since an analysis is comprised of many different low level elements that are shared and managed and moved around to be as efficient as possible. Therefore its not really possible to correlate the exact RAM utilization with a particular analysis.
Issue/Introduction
This article describes different ways to find the analysis which consumes more memory in troubleshooting Web Player's high memory utilization
Resolution
While there is no way to find the exact amount of memory utilized by an analysis which is opened on the Web Player, there are some methods you can use to get some information related to the amount of memory consumed by the analysis in Schedule Updates:
1. For a RAM usage estimate: You can load the report in Spotfire installed client or an otherwise unused Web Player instance and check the process size in Task Manager. This is the most accurate method. Note: If the report uses personalized information links or imports other data during user sessions with on-demand data tables, data functions, etc, then you must also consider that when comparing the size seen in this test.
2. For a relative comparison of size/complexity: You can also look at the Monitoring & Diagnostics > Instances > Select Web Player instance > Analyses and Diagnostics which has table size and node counts of the opened analyses.
A Document Node is a building block of our code that holds a value or object that has a state. Depending on how each feature or detail is implemented one Document node can hold a single value, or a complex structure. The number of document nodes is exposed as a way to report on the consumption of .NET memory together with the data table and view size and execution time per analysis which is also shown. This information helps to understand which analyses consume the most resources (not available before version 6.0)
1. For a RAM usage estimate: You can load the report in Spotfire installed client or an otherwise unused Web Player instance and check the process size in Task Manager. This is the most accurate method. Note: If the report uses personalized information links or imports other data during user sessions with on-demand data tables, data functions, etc, then you must also consider that when comparing the size seen in this test.
2. For a relative comparison of size/complexity: You can also look at the Monitoring & Diagnostics > Instances > Select Web Player instance > Analyses and Diagnostics which has table size and node counts of the opened analyses.
A Document Node is a building block of our code that holds a value or object that has a state. Depending on how each feature or detail is implemented one Document node can hold a single value, or a complex structure. The number of document nodes is exposed as a way to report on the consumption of .NET memory together with the data table and view size and execution time per analysis which is also shown. This information helps to understand which analyses consume the most resources (not available before version 6.0)
Additional Information
Doc: Examining the statistics of an individual analysis
Doc: Performance troubleshooting
Community: Spotfire Web Player Capacity Planning
Feedback
Yes
No
Powered by
