Performance Tuning in SAP BI/BO

SAP BO Performance Tuning @ Various levels:

Connection Level: Use 64 bit connection types @64 bit Operating System rather 32 bit connection type.

Database Level/OLAP cubes/BEx Queries: Healthy DWH or well design of Database, its tables with Indexes built.

Semantic/Universe Level:
Formulas, Aggregate functions, Aggregate_Awareness, LOVs, Group by, Prompts based on Year, Quarter, Month, Weeks, Day at Database level, Aggregated/Pre-calculated Tables.

Array fetch size: 
Increase Array fetch size at Universe Designer Level.

Suppose if we have a report with 5000 Rows, if the Array Fetch size is 100 then BO server connect with the back-end database 50 times. Each Time BO server fetches 100 records.

Client Tools/Report Level:

Web Report:
Crystal Report:
Dashboards:

As part of Maintenance activities, clear caches,GC With scheduled restart on production on Non-Business Hours.

Server Level:
Split APS for Webi, Crystal, Dashboard services.
Configure DSL Bridge. 
Clone multiples of 1 service in CMC, Have separate job servers.

Load Balance in production server can be handled by CMS level clustering.

Disaster Recovery (DR), have a separate server with clone of production server in different location, as a standby server.

Hardware/Network Level:
Increase the RAM
Increase space/shift the path of IFRS/OFRS files to other location.
Configure Gigabyte LAN Cards across the OS server, DB, WebServer within Enterprise (Network/LAN)

Maintenance Activities:
Daily: Sanitize un-used objects.
Weekly:Clear caches and Scheduled instances.
Monthly: Restart.
Quarterly: Update software patching.