I had set ulimit to unlimited, so i am not sure how much is locked by timesten.
Is there any way to know how much memory timesten has locked?
Is it PermSize + TempSize + LogFileSize + LogBufMB?It is effectively PermSize + TempSize + LogFileSize + LogBufMB _ small overhead (around 20 MB in current release). The best way to get an exact figure is to use O/S 'ipcs' command to see exact size of Timesten datastore segment.
About your previous message, regarding AWT write up to oracle.
A secondary, but major, concern is this:
Just want to understand, does writing of replication agent towards oracle impact the overall response time?
I must be wrong but my understanding was that timesten will take writing towards oracle asynchronously for AWT cache groups.
It will not impact my application performance.
Sorry, but just want to understand the behavior.AWT cache groups are asynchronous so thgere is no direct impact on application performance. However, when replication (and AWT is included in this) enters any kind of backlog situation the replication agent has to start capturing changes from the logs on disk instead of from the in-memory log buffer (the evidence that thsi is happenning is the increasing value of LOG_FS_READS). This results in a very large increase in I/O (IOPS) on the device(s) holding the datastore's log files (it essentially changes from sequential I/O to random I/O) and this will impact the system as a whole and may especially impact TimesTen logging both of which can lead to reduced performance, increased/unpredictable response time etc.