Improving Actuate Reporting Performance in Clarity
10. Optimizing Memory
Actuate recommends a minimum of 1GB of RAM per CPU for Large Workloads.It is important not to use up all available memory.When CPU Requires more memory than available.There must be standards for each server like WebbLogic,Webshere and Tomcat,stick on that.
11.Run the Remove Job Logs and Report Library Entries
This job removes job log and Report Library entries from databases that are
older than a specified number of days.Schedule it weekly.
12.Schedule the Reports
During High Traffic Times Run large reports by scheduling rather running immediately and also if possible
schedule it on Non Peak Hours.
13. Seperate Server for Reporting
To provide for sufficient resources for both Application and Database servers, place the report server on a different CPU from the database or application server . Both report generation on the report server and database or application server tasks are CPU-intensive. If you cannot place the report server and database server on separate CPUs, plan for additional CPU, memory, and disk resources to support the report server.
14. Check All Resource Utilizing
Check the Operating System resources including I/O ,Network ,CPU and Memory.
15. Monitor the Reporting Performance
Monitor the Report performance via OS Utilities at regular Intervals which will help you to analyze Performance.
* For windows -- Windows Task Manager,Windows Performance Monitor.
* For Unix -- Top,Vmstat,iostat,netstat,sar
Reporting Performance issue is very common and an challenge to address it.I faced that and managed to overcome with the help of experts advice and some ground work.i worked and tested in throwly in Test server and then implemented in Production.This is specific to Actuate Reporting.
1. Tuning the Sql
In Most situations the poor performance of Reports is due to inefficient Sql.Pls extract the SQL queries to run them directly against the database to measure the Performance.Tuning your SQL is often the best way to increase overall Reporting performance.
2. Minimise the data
Minimise the data in your report at every opportunity. Only bring back records that are required.That will improve the reporting performance significantly.Less Data More speed.Optimize the Tables & Indexes.
3. Run acverify utility Monthly.
The acverify command-line utility validates an Encyclopedia volume and optionally attempts to repair problems found in the volume. Use acverify with an offline volume.It cannot be used with an online volume.
Command:- Run acverify check all repair
4. Archiving
Clear the Old Archival Files which will Free enough space and will boost the Reporting server performance.
A) Setting archive folder
Create a new environment variables in the actuate server called AC_ROOT_FOLDER and set the archive folder.
B) Setting the archive library
Login to Actuate Management Console System Administration, click at System Volumes -> General. Enter the archive library path into the archive library name. The archive.dll usually located in the Actuate9\iServer\Examples\Archive folder.You need to restart the server for this field to take effect.
C) Setting archive rules
Login to Actuate Management Console System Administration then go to the Files and Folder(where the roi files resides,usually /cus/) and right click properties and then select the file type to archive (Actuate Report Document - roi) and choose the Archive files before deletion Option.
This option will archive the files to the archive folder before the file is deleted. This is useful to recover the report at a later stage.However, this will add on additional disk space in the server as it will be keep as an archive file.So probably after some time you can delete the Files.
D)Setting archive schedule
Login to Actuate Management Console System Administration thenClick at Volume -> Archive Schedule then Select the start date and time to start the schedule. Advise to start the archive schedule during non peak hours and the time doesn’t clash with the backup schedule.
5. Increase the Buffer pool size
In Actuate Management Console System increase the Buffer pool size where the default is 10mb.Actuate iServer manages this information using a page buffer pool.Actuate recommends setting the buffer pool as large as possible to keep the buffer pool data in the Actuate iServer machine’s memory and not in the machine’s disk swap space.
6. Adding Factory processes (Important)
In both stand-alone and cluster configurations, the optimum number of Factory processes for Actuate iServer depends on the speed of the CPU that runs the Actuate iServer workload and the mix of reports in the workload.To begin, configure two Factory processes on a processor. Adding Factory
processes can enhance performance if the database that Actuate iServer uses to create reports is a performance-limiting resource.
Actuate iServer can use the multiple Factory processes to run multiple, simultaneous reports that use the database. When Actuate iServer runs multiple, simultaneous reports, some of the Factory processes access the database while other Factory processes perform report generation tasks that do not access the database.
7. Increase the View Server Performance.
The default value is 50, which means 50MB.You can increase the file size accordingly.The View process maintains caches for reports and report executable files. You can set Actuate iServer parameters to configure cache sizes, time-out values, and other View process parameters. In most cases, you do not have to change the values for these parameters from the default values.
The View process stores session information in a cache. Increasing cache size can improve View process performance when cache size is a limiting resource. The View process uses cache to store ROX files and view session information.
8. Improve report generation for long running reports
Improve report generation for long running reports by increasing the value of the environment variable.The default is 15 seconds, you can increase to 30 seconds.
AC_FACTORY_PAGE_COUNT_UPDATE_INTERVAL -- default is 15 seconds.
9. De fragmenting the Report Encyclopedia
To improve Report Encyclopedia performance, run the ACDEFRAG utility on a regular basis. Alternatively, back up and restore the Report Encyclopedia using the ACEXPORT AND ACIMPORT utilities on a regular basis.
1. Tuning the Sql
In Most situations the poor performance of Reports is due to inefficient Sql.Pls extract the SQL queries to run them directly against the database to measure the Performance.Tuning your SQL is often the best way to increase overall Reporting performance.
2. Minimise the data
Minimise the data in your report at every opportunity. Only bring back records that are required.That will improve the reporting performance significantly.Less Data More speed.Optimize the Tables & Indexes.
3. Run acverify utility Monthly.
The acverify command-line utility validates an Encyclopedia volume and optionally attempts to repair problems found in the volume. Use acverify with an offline volume.It cannot be used with an online volume.
Command:- Run acverify check all repair
4. Archiving
Clear the Old Archival Files which will Free enough space and will boost the Reporting server performance.
A) Setting archive folder
Create a new environment variables in the actuate server called AC_ROOT_FOLDER and set the archive folder.
B) Setting the archive library
Login to Actuate Management Console System Administration, click at System Volumes -> General. Enter the archive library path into the archive library name. The archive.dll usually located in the Actuate9\iServer\Examples\Archive folder.You need to restart the server for this field to take effect.
C) Setting archive rules
Login to Actuate Management Console System Administration then go to the Files and Folder(where the roi files resides,usually /cus/) and right click properties and then select the file type to archive (Actuate Report Document - roi) and choose the Archive files before deletion Option.
This option will archive the files to the archive folder before the file is deleted. This is useful to recover the report at a later stage.However, this will add on additional disk space in the server as it will be keep as an archive file.So probably after some time you can delete the Files.
D)Setting archive schedule
Login to Actuate Management Console System Administration thenClick at Volume -> Archive Schedule then Select the start date and time to start the schedule. Advise to start the archive schedule during non peak hours and the time doesn’t clash with the backup schedule.
5. Increase the Buffer pool size
In Actuate Management Console System increase the Buffer pool size where the default is 10mb.Actuate iServer manages this information using a page buffer pool.Actuate recommends setting the buffer pool as large as possible to keep the buffer pool data in the Actuate iServer machine’s memory and not in the machine’s disk swap space.
6. Adding Factory processes (Important)
In both stand-alone and cluster configurations, the optimum number of Factory processes for Actuate iServer depends on the speed of the CPU that runs the Actuate iServer workload and the mix of reports in the workload.To begin, configure two Factory processes on a processor. Adding Factory
processes can enhance performance if the database that Actuate iServer uses to create reports is a performance-limiting resource.
Actuate iServer can use the multiple Factory processes to run multiple, simultaneous reports that use the database. When Actuate iServer runs multiple, simultaneous reports, some of the Factory processes access the database while other Factory processes perform report generation tasks that do not access the database.
7. Increase the View Server Performance.
The default value is 50, which means 50MB.You can increase the file size accordingly.The View process maintains caches for reports and report executable files. You can set Actuate iServer parameters to configure cache sizes, time-out values, and other View process parameters. In most cases, you do not have to change the values for these parameters from the default values.
The View process stores session information in a cache. Increasing cache size can improve View process performance when cache size is a limiting resource. The View process uses cache to store ROX files and view session information.
8. Improve report generation for long running reports
Improve report generation for long running reports by increasing the value of the environment variable.The default is 15 seconds, you can increase to 30 seconds.
AC_FACTORY_PAGE_COUNT_UPDATE_INTERVAL -- default is 15 seconds.
9. De fragmenting the Report Encyclopedia
To improve Report Encyclopedia performance, run the ACDEFRAG utility on a regular basis. Alternatively, back up and restore the Report Encyclopedia using the ACEXPORT AND ACIMPORT utilities on a regular basis.
10. Optimizing Memory
Actuate recommends a minimum of 1GB of RAM per CPU for Large Workloads.It is important not to use up all available memory.When CPU Requires more memory than available.There must be standards for each server like WebbLogic,Webshere and Tomcat,stick on that.
11.Run the Remove Job Logs and Report Library Entries
This job removes job log and Report Library entries from databases that are
older than a specified number of days.Schedule it weekly.
12.Schedule the Reports
During High Traffic Times Run large reports by scheduling rather running immediately and also if possible
schedule it on Non Peak Hours.
13. Seperate Server for Reporting
To provide for sufficient resources for both Application and Database servers, place the report server on a different CPU from the database or application server . Both report generation on the report server and database or application server tasks are CPU-intensive. If you cannot place the report server and database server on separate CPUs, plan for additional CPU, memory, and disk resources to support the report server.
14. Check All Resource Utilizing
Check the Operating System resources including I/O ,Network ,CPU and Memory.
15. Monitor the Reporting Performance
Monitor the Report performance via OS Utilities at regular Intervals which will help you to analyze Performance.
* For windows -- Windows Task Manager,Windows Performance Monitor.
* For Unix -- Top,Vmstat,iostat,netstat,sar
