Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Management Metadata design as it impacts performance Data volume and content measurement Rules performance measurement Reading the HFM logs
Application Profile
Year No inherent impact on performance Cannot be changed after the application is built Impacts the number of tables that can be created in the database Period The base periods comprise the column structure of every table, whether you use them or not. For this reason, avoid weekly or yearly profiles unless it is key to your entire applications design View No impact, but only YTD is stored and Periodic, QTD are on-the-fly derivations
Whats a Subcube?
HFM data structure Year, Scenario, Value, Entity Database tables stored by Each record contains all periods for the [Year] All records for a subcube are loaded into memory together
Parent subcube, stored in DCN tables Currency subcubes, stored in DCE tables
Accounts
Entities Currencies Custom1 Custom2
2,132
1,165 16 388 153
14,409
22,882 233 19,410 15,188
use only
1 currency 30%
Custom3
Custom4 Scenarios Entity hierarchies ICP Accounts with Plug
61
39 11 3 41
26,816
11,389 78 24 1,223
the equivalent of Organizations in Hyperion Enterprise use automated intercompany matching 56%
36
5
1,667
10
16% use this, but only 10% have more than 1 account flagged
use consolidation rules 28% use methods 14% use organization by period 9%
86 143 5
1,407 7,698 53
track intercompany activity 81% Allow [Parent Adj] or [Contribution Adj] journals30% use process management46%
Data Design
Metadata volume is interesting, but its how you
Density
Content Specifically: zeros Tiny numbers Invalid Records
Loaded Data
What percent of the loaded data is a zero value?
No hard rule, but <5% may be reasonable
Watch out for tiny values, resulting from allocations How much does the data expand from Sub Calculate?
Am I generating zeros, or tiny numbers?
Input Base Records Total Input zeros % zero loaded Input Plus Calculated Base Records 2,031,976 Total 18,024 Calculated zeros 0.9% % zeros calculated at base 4,387,520 413,837 9.4% % Increase From Rules
116 % 2,196 %
593,981
13.5%
59 %
NumCubesInRAM
NumDataRecordsInRAM NumRecordsInLargestCube Average records per cube
2,672
1,502,788 86,415 6,309
72
10,206
1,345
577
1,107,614 31,446 2,288
7.3%
0.3%
39.7%
3.4%
7.3%
Rewrite the rule for optimal performance Lets focus on the top 10
Establish a Baseline
Performance begins with perception. Establish this and a baseline before applying science.
Chris Barbieri Sr. Product Issues Manager Hyperion Solutions March 5, 2006
Effect of caching Data cache on database server AND on HFM application server Caches may be empty during first run Performance is significantly better when data reads comes from memory cache rather than disk
Run the same process 3 times in a row and use the average
Rules of Thumb
Most application between 0.25 and 2.0 seconds per entity, per period Consolidate all with data for entire hierarchy, full year Divide by total number of entities (descendents of selected parent), divided by 12 periods Most applications are closer to 0.25 seconds Rules Impact Ratio Blank rules file, Consolidation Rules = N for baseline Divide consolidation time with rules by time without Usually 2-5 times
Records
1.500
1.000
correlation between density and calc times Most applications are rules bound When HFM app server CPU is < 20%, it is communicating with the database server
Messages are informational start/stop consol, log in, log out etc. Some messages are purposely out of time order (consol starts get printed at completion of consol Often due to subcube size issues HFM Subcube Troubleshooting Guide / Memory Management in HFM documents Access rights Syntax Issues
Warnings
Errors
HFMErrorLog Viewer.exe
System
Details
Web suppresses
Find Registry
application start-up. Most but not all registry entries are written Well cover the actual entries in another presentation
Paging
Watch PageOutOps > 0 indicating page file usage
indicates start time Details have finish time Is written when it completes
database You can extract the database entries to a text file, which is preferable to the event logs Can also truncate the entries using this utility And split large files (anything > 30 MB is too large)
Chris Barbieri
Established HFM performance tuning techniques and statistics widely used today
4+ years as Sr. Product Issues Manager at Hyperion
Kurt Schletter
Over 20 years in IT
Hyperion Support Manager at United Technologies, serving 3,600+ HFM users 5+ years Hyperion product
infrastructure services MBA, Rensselaer Polytechnic Institute B.S. Management with Computer Applications, Worcester Polytechnic Institute
Visit www.Ranzal.com/News.htm
Chris Barbieri
cbarbieri@ranzal.com Needham, MA USA +1.617.480.6173 www.ranzal.com