How can we do performance tuning for reports ?
Developer_Designer (BOB member since 2009-08-09)
Performance is a broad subject, with many factors coming into play, such as how many rows your query returns, universe design, the underlying DB architecture (star schema, normalized structure, oltp database), aspects of the physical database design (indexes, views, key structure, etc), the BO architecture (how many servers, which services and how are they configured, where is the FRS located, etc), the hardware (CPUs, network speed, load balancing, etc) to name a few. And on and on.
All these things effect performance. So it depends on which of them are under your control. Constrain the query to return as few rows as possible to satisfy the requirement for starters. Similarly, make sure only tables needed to satisfy the requirement are included in the joins.
charlie 
(BOB member since 2002-08-20)
(BOB member since 2008-05-12)Charlie thanks a lot for small and nice explanation. Can you just explain how the location of FRS affects report performance? Thanks in advance.
aniketp 
(BOB member since 2007-10-05)
If your FRS (input and output) are on faster devices, such as a SAN, I/O for reading in your universe and report, and writing out instances will be faster. This is probably not going to yield as big an improvement as doing something to eliminate a join, for example.
charlie (BOB member since 2002-08-20)