Skip to main content

Improving Hyperion Planning Application


There are three things you can do to improve the performance of the Planning application.

I. Increase the Java heap size:
You can increase the heap to a maximum of 1Gb (1024Mb). If you have the available RAM to dedicate to Planning, it is recommended to increase both the minimum (Xms) and maximum (Xmx) heap size to 1024Mb. Increasing the minimum heap size will help because it lowers the overhead needed to manage garbage collection in a dynamically expanding heap. Do not exceed 1024Mb or you may see performance actually decrease. The step by step procedure for modifying the Java heap size varies from one web application server to another. Contact your web application administrator for assistance.

II. Turn off process management for Version and Scenario members for which it is notneeded:
 By default, new Scenario and Version members are enabled for process management.Each Entity-Scenario-Version combination (each Planning unit) costs resources becausePlanning must check who currently owns the Planning unit and check the security settings. If you have many Scenarios and Versions the number of combinations increases rapidly. Decide what Versions and Scenarios need to be available for process management, and then disable the others. If you are not using process management at all then you can disable process management support for all Version and Scenario members. To disable process management support, edit a member of the Scenario or Version dimension. In the member properties, uncheck the "Enable for process management" checkbox. Repeat for each member you want to disable process management for. When finished, do a database refresh using the Administration>Manage Database page and restart the Planning service.

III. Optimize the design of web forms:
Large web forms impose by far the heaviest load on the Planning JVM. Optimizing the design of forms can make a big difference to how fast a form opens and how many users can open it concurrently


Popular posts from this blog

Essbase for Beginners: Data Block concepts Part A

An Essbase outline has a number of dimensions.  The number of dimensions can range in quantity and size, but each dimension is identified as a dense or sparse dimension.  As we understood the concept of Dense and Sparse in our last discussion, let’s begin with the cocept of data blocks now. To understand this, let’s carry forward our hierarchy of 5 dimensions in a test application in my previous post.. We have 3 dense and 2 sparse dimensions each with 3 stored members. So let’s begin: Number of Existing Blocks = (potential number of blocks) * estimated density= 9 Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3 *8 = 216 Potential number of blocks = Sparse Stored * Sparse Stored = 9 If all dimensions are assigned as Dense, Number of Existing Blocks = (potential number of blocks) * estimated density= 1 Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3*3*3 *8 = 1944 Potential number of bloc...
Home

Shared Connection and Private Connection

You connect to data sources through shared or private connections. Shared Connections •Shared connections are stored in a central location and are available to multiple users through the Smart View Panel. You cannot add, edit, or rename shared connections, but you can save them as private connections, which you can edit and rename. Private Connections •Private connections are those that you create by saving a shared connection to your local computer or by entering a URL to a provider that is not configured for shared connections. When you create a private connection, it becomes the active connection. Shared Connections : 1. From the Smart View ribbon, click  Panel . 2. From Smart View Home or from the menu displayed when you click the arrow next to Home button, do one of the following: • Click a connection name under  Recently U sed . You can click    to pin items to this list. • Select  Shared Connections  to open th...
Home

Essbase for Beginners: Data Block concepts Part B

Below concepts involve Data Blocks in some way or the other, so to understand how Data Blocks behave it’s good to understand these concepts: Let's Begin!! Compression Clean and Dirty Blocks Fragmentation Restructure Compression: When Essbase stores blocks to disk, it can compress the data blocks using one of the following compression methods, this is based on the type of data that is being loaded into the Essbase database. Essbase provides several options for data compression: 1. Bitmap compression : This is the default compression method. Essbase stores only non-missing values and uses a bitmapping scheme. A bitmap uses one bit for each cell in the data block, whether the cell value is missing or non-missing. When a data block is not compressed, Essbase uses 8 bytes to store every non-missing cell. 2. Run-length encoding (RLE): Essbase compresses repetitive, consecutive values --any value that repeats three or more times consecutively, including...
Home