How to Improve the Performance of Hyperion Financial Management SmartView Workbo

gaoyiming

1. SubcubesYour SmartView workbook will update more efficiently if it accesses as few subcubes as possible. A subcube is defined as all the records where Scenario, Year, Entity and Value are the same.

Page and Sub-cube Dimensions

Page Dimensions	Subcube Dimensions
Scenario	Account
Year	Intercompany Partner
Entity	Custom 1-4
Value Triplet	Period
	View

You should therefore try to restrict each worksheet to one or two scenarios, years, entities and values (e.g. currencies). On the other hand, accounts, periods and custom dimensions are part of the same subcube, so may be freely mixed.
As subcubes are loaded into memory on the HFM application server, you may need to monitor memory usage, the Task Audit, and general server performance during a SmartView refresh. Check the HFM event log (HsvEventLog.log) for frequent FreeLRUCachesIfMoreRAMIsNeeded messages during a single retrieve, in which case additional server RAM may be needed.
2. Function designWe often see clients creating SmartView functions that list all 12 dimensions. This increases the size of the workbook, increases the amount of data send to and from the server and prevents SmartView using POV caching efficiently. Instead, rely on the Background POV, which you set via POV Manager, for the majority of your dimensions and only code the exceptions into each function. This is the best optimisation to employ when the network is identified as the bottleneck.
3. Adhoc rather than functionsAdhoc queries are inherently more efficient than functions. If a worksheet can be set up as an Adhoc grid, performance will benefit.
4. Use Hyperion ReportsResist the temptation to turn Smart View into a portable database. Use SmartView for its primary purpose of ad-hoc financial analysis and use Hyperion Reports for long reports.
5. Upgrade SmartViewStarting at version 9.3.1, SmartView started using HTTP compression to reduce network traffic. An upgrade to this version or later would be indicated if the network significantly lengthens refresh times. There is a slight cost to processing time.
6. Upgrade the client PCIn normal use, the majority of the time spent during a refresh is on the client, as it formats the data to send to the server, parses the reply and feeds the values into Excel, and while Excel recalculates. Ensuring that end users have machines with sufficient RAM and adequate powerful CPUs will benefit them most, if other bottlenecks have been eliminated. We suggest 1-2 GB RAM when large workbooks are being used.
Summary1. Avoid accessing more than 2 or 3 sub-cubes.
2. Rely on the background Point of View and shorten SmartView functions.
3. Adhoc rather than functions
4. Use the most appropriate tool for the job
5. Use HTTP compression (version 9.3.1 on, though not recommended before 11.1.2)
6. Upgrade the client PC