Estimating Temporary Space Required For A TimesTen Data Store
Last updated on SEPTEMBER 23, 2016
Applies to:TimesTen Data Server - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.0 to 11.2]
Information in this document applies to any platform.
This Note will be of interest to all developers and DBAs working with TimesTen data stores. The method discussed applies to all production releases of TimesTen.
***Checked for relevance on 06-Nov-2013***
The significant data structures in a TimesTen data store include the permanent data region (PermSpace), the temporary data region (TempSpace) and the log file buffer (LogBuffSize in V7; LogBufMB in V11). The temporary region holds various temporary structures as well as transaction control information, locks, etc. The space required for the temporary region is very much dependent on the nature of the application, the number of concurrent users, the size of various transactions in the system. It is quite possible for 2 different applications to have the same size permanent data region and very different temporary data region requirements; while the amount of permanent data in the data store may be the same in both data stores, the transaction volume and size of each transaction may be totally different. Consequently, it is difficult to calculate the amount of space needed for a data store's temporary region.
This Note offers a suggested method for estimating the space of a TimesTen temporary region, i.e., the value of the TempSpace parameter. The method assumes that PermSize has already been calculated.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms