This content has been marked as final. Show 10 replies
user9952742 wrote:We are using both SmartView and Financial Reporting. Using SmarView reports is much faster than FR reports.
Does anyone know how to make Essbase reports in Workspace run and print faster?
We currenty just migrated to Essbase Sys9. We used to have all Essbase canned reports in Excel, and had really no problems with the speed. However, when we migrated to Workspace, the speed on running the reports as well as printing them is so much slower than doing everything in Excel. Does anyone have the same problem? Or do we need to configure any setting to make them run and print faster?
How are you building your reports in Workspace? Do you use Web Analysis, Financial Reporting or Interactive Reporting?
In general as a rule (although there's bound to be differences), Financial Reporting reports should run from the Workspace as fast as they can run via spreadsheet.
However you need to remember there is a report server and also print server generating images, so depending on your configuration they can impact the reports. Below is some info, from an interRel presentation I sat in on a few years ago:
- Grid Point Of View
- Limit Page Members for PDF Viewing
- Limit Conditional Formatting
- Limit Number of Combinations
- Utilize expanded data segments when possible
- Increase Cache Settings
- Consider Density/Sparsity Changes
- Push calculations to the Hyperion Essbase Server
Multiple Print Servers:
Multiple print servers assist in generation of PDFs. The report server will distribute print jobs in a round robin format to multiple print servers, providing a shared workload.
1. Stop all Hyperion Reports services
2. Open with Notepad the hr_repserver.properties file located in "C:\Program Files\Hyperion Solutions\Hyperion Reports\Packages".
3. Next to the setting "NumberOfPrintServers=", specify the number of print servers you will use.
4. Add an entry for each print server and specify the machine name or IP address of each Print Server in the following convention: printserver1=machineA
5. On each print server, install Adobe Acrobat Writer or Ghostscript and install Hyperion Reports. During the installation of Hyperion Reports, select the box to install only the Print Server.
6. On each print server, execute the print server batch file through START->PROGRAMS->HYPERION SOLUTIONS->HYPERION REPORTS->START PRINT SERVER or by double-clicking StartPrintServer.cmd file located in "C:\Program Files\Hyperion Solutions\Hyperion Reports\Bin"
7. Start the Hyperion Reports Services in the Hyperion Reports server.
Ghostscript vs. Adobe:
GNU Ghost Script 7.0.6 and AFPL Ghostscript 8.14 is recommended over Adobe Distiller as Ghostscript allows for parallel print processing.
The Print Server can handle multiple requests at once because each request is run on its own execution thread. This is helpful when you have a number of users generating PDFs at the same time.
Using AFPL Ghostscript enables the following two features: — Copy multi-byte text from PDF to clipboard — Enable searchable PDF files
Updated by: icurtain on Aug 19, 2009 12:48 PM with Presentation info
In what aspect of the Grid Point of View? Is it from a user's perspective, such as making sure his preference is set to POV On, or is in FR studio where as much as possible we as admin should choose User Point of View instead of Respond to Prompts?
I was looking for hr_repserver.properties, but only found fr_repserver.properties. Also, there I could find anything that says "numberofPrintservers", only ReportServerStartupThreads. Are they the same?
# Report Server startup settings
# Specify the number of threads created for running reports at startup time.
# The default is 10.
# Specify the maximum number of threads created for running reports at any time.
# The default is based on the number of CPU's in the host machine - 5 threads per CPU.
# 1 CPU -> 5 threads , 2 CPU's -> 10 threads, 3 CPU's -> 15 threads, 4 or more CPU's -> 20 threads
# Specifying 0 will allow an unlimited number of threads to be created.
Grid point of view relates to putting as many members in the POV as this will speed up the report run time. It's much more efficient because the report server has one distinct member or slice to look up the data on.1 person found this helpful
hr_repserver.properties is not the same as fr_repserver.properties, it should be located in the following directory: \Hyperion\HyperionReports\lib\
Since for the FR reports, the server is not taking care of reading the data from essbase and displaying it on the report, but it also takes care of: suppressions, formattings, conditional formattings, calculations on report level, generating the pdf output etc..
but for the excel reports, formatting has already been done, calculations on report run on the client machine,,,, but of course there are disadvantages of using excel report packs, as you cannot use dynamic lists like descendants etc,, maybe you can achieve this by using vba but it will not be so easy... POV selection lists will not be dynamic either. you cannot do suppressions, (maybe you can by using vba, but it will be a lot of coiding)...
how did you take care of these disadvantages in your excel report pack?
Interrel also advise FR admins to not run FR reports using the same logins. Someone at Interrel said that reusing LOGIN ID's confuses FR and will slow FR reporting.
The same log-ins to the FR admin's Essbase/HFM log-ins? Does that mean the admin's username and password for FR should not be the same as the admin's username and password in Essbase/HFM?
We had a lot of VB and Excel functionalities in our Essbase Excel based reports...