BITMAP INDEXING ON KEY COLUMNS

cache
aggregate table
connection pool
DDR
Multiple LTS
connection pool

INFORMATICA
------------
Network:The performance of the Informatica Server is related to network
connections.
Data generally moves across a network at less than 1 MB per second, whereas a local
disk
moves data five to twenty times faster. Thus network connections often affect on
session performance.
So avoid network connections.

Drop constraints: If target consists key constraints and indexes it slows the
loading of data.
To improve the session performance in this case drop constraints and indexes
before we run
the session(while loading facts and dimensions) and rebuild them after completion
of session.

Parallel sessions:Running a parallel sessions by using concurrent batches will also

reduce
the time of loading the data. So concurrent batches may also increase the session
performance.

Filter Transformations:

Run the informatica server in ASCII data movement mode improves the session
performance.
Because ASCII data movement mode stores a character value in one byte. Unicode mode
takes 2 bytes to store a character.

Group transformations: Aggregator, Rank and joiner transformation may often

decrease the session performance.
Because they must group data before processing it. To improve session performance
in this case use sorted ports
option ie sort the data before using the transformation.

Lookup Transformations: If the session contained lookup transformation you can

improve the session
performance by enabling the look up cache.The cache improves the speed by saving
the previous data and
hence no need to load that again

cache
Increase performance by indexing the primary key-foreign
keys if the source table has more than 1,000 rows
Improve session performance by caching small lookup tables
Use reusable Lookup transformation instead of using same
Lookup Transformation multiple times
Use source filter in the Properties tab to reduce the number of rows
Reduce the number of transformation.
Delete unnecessary links between transformations to
minimize the amount of data moved, especially in the Source Qualifier
 Plan for reusable transformations
Use mapplets to encapsulate multiple reusable transformations.
Use variable ports to calculate a value that can be used multiple times
Numeric operations are faster than string operations
Operators are faster than function. Example: || is faster than concat()

Below are the options to improve performance:

Mapping level changes-->
1. Move the filter T/f as close to source as possible.
2. Use override queries in SQ t/f and Lookup t/f to get data that we need.
3. Use a sorter t/f or use order by clause in SQ t/f before joiner Aggregation t/f
4. If lookup is taking lot of time, make it as a source and use left outer join.
5. Create indexes on the column we use for joins

Session level changes -->

1. Increase Commit interval
2. Increase DTM buffer size
3. Session Partitioning
4. Use normal Verbose level

Performance Tuning With DAC

---------------------------
DAC provides functionality related to indexes, tables, tasks, and workflows that
enables you to enhance performance.

Managing Indexes

Using Actions to Optimize Indexes and Collect Statistics on Tables

Using Heuristics to Manage Tasks, Tables and Indexes

Looping of Workflows

Customizing customsql.xml to Drop and Create Indexes and Analyze Tables