Application Is Slow

For details on how to maximize the performance of your application and TimesTen database, see:

This section describes some issues that impair performance.

Possible cause See...

Using client/server mode.

Consider Connection Mode for information.

Database statistics are outdated.

Update Statistics for Your Tables for information.

Committing transactions too frequently.

Turn Off Autocommit Mode in the Oracle TimesTen In-Memory Database Operations Guide.

DurableCommits attribute is enabled.

Use Durable Commits Appropriately in the Oracle TimesTen In-Memory Database Operations Guide.

SQL statements used more than once are not prepared.

Prepare Statements in Advance in the Oracle TimesTen In-Memory Database Operations Guide.

There is a wrong kind of index, too many indexes, or a wrong size for hash index.

Select the Appropriate Type of Index in the Oracle TimesTen In-Memory Database Operations Guide.

Size Hash Indexes Appropriately in the Oracle TimesTen In-Memory Database Operations Guide.

Use of locks is inefficient.

Verify Lock and Isolation Levels for information.

Operations are slightly slower when performed on out-of-line columns versus inline.

Inline and Out-of-Line Columns in the Oracle TimesTen In-Memory Database Operations Guide.

Materialized view is improperly configured.

Performance Implications of Materialized Views and Materialized View Tuning in the Oracle TimesTen In-Memory Database Operations Guide.

If replication is used, configuration of replication scheme or network environment may be impacting application.

Poor Replication or XLA Performance for information.

If TimesTen Cache is used, TimesTen Cache configuration or environment may be impacting application.

Poor Autorefresh Performance for information.

There are too many table partitions.

Check Partition Counts for Tables for information.

Tracing is unnecessarily enabled for one or more TimesTen components.

Check Trace Settings for information.