Microsoft Office Tutorials and References
In Depth Information
Figure 6-15. The “Delete Comments by Date” dialog
The cache section of the page contains a single entry that sets how long (in seconds) the images associated with KPIs
should remain in memory before the memory is reclaimed. The default is 10 seconds, which should allow the image
to be reused several times during the rendering of a single page. If your site makes heavy use of only a few unique
indicators, it might make sense to extend this value to keep from frequently reloading them from disk.
Analysis Services EffectiveUserName
This setting enables PPS to pass in the current user name in the connection string ( ;EffectiveUserName=domain\UserName )
when making a connection to SSAS data source. SSAS filters the data based on the user name passed in the
connecting string. For this setting to work, the managed service account used for PPS should have administrative
rights in the SSAS server.
This section allows the administrator to set a standard timeout on a data source, preventing pages from becoming
unresponsive when a data source becomes slow or unavailable. The default is 300 seconds, which should be sufficient
in most cases. If data access is consistently over 5 minutes, either the data source is not responding properly or the
queries being used to access the data should be reconsidered. When data access for a dashboard page takes a very
long time, two major problems result.
First, system resources are consumed processing and returning large amounts of data that will, most likely,
never be used. The thread, table, memory, and I/O locking and contention created by executing very large queries
can quickly diminish system performance for all users.
Second, users are not going to wait for several minutes each time they interact with the dashboard. A user
viewing a dashboard is trying to avoid information overload, so loading 1,000 or more records defeats this purpose.
Long wait times degrade the user experience and lead to having dashboards that aren’t used.
Filters are used on dashboards to set how the data is “sliced.” PerformancePoint dashboards have the ability to
remember the last filter values used by each user. This is valuable when moving from one dashboard page to another
or when returning to a dashboard on a future visit.
To avoid storing this data forever, this configuration section allows the administrator to set a time out (in days)
for how long to retain unused filter values.
The maximum number of members that can be loaded into a filter tree (shown in Figure 6-16 ) is configured here
as well. Each time you use a filter, you are selecting a set of values to apply with the filter. For example, if you select the
year 2010 at the Months level of the date hierarchy, you are selecting 12 values that must be stored for the filter. If you
are selecting at the Day level, there are 365 values that must be stored. Each of these values is called a “member” of the
filter. This setting prevents very large selection lists from slowing down the server for all users.
Search JabSto ::