Thank you for your detail guidance, it really helped.
Yes, I am planning to optimize my application to see if memory usage can be reduced.
But do you have any other suggestion from the above monitor output.
One thing I am planning is to reduce PERM_ALLOCATED_SIZE=4196352 cause I see that PERM_IN_USE_HIGH_WATER=2697380.
Also TEMP_ALLOCATED_SIZE=1048576 to TEMP_IN_USE_HIGH_WATER=46384
Do you think from the monitor output, there is still something I can do with timesten?
There is nothing else that looks 'bad' in the monitor output. It does seem like you can reduce the memory allocated to perm and temp somewhat and this will help with the general memory usage on the machine. Just be careful you don't reduce it too much. Some things can cause temporary increass in memory requirements (reflected by the HIGH_WATER metrics) and of course if you start storing more data in TimesTen then Perm usage will increase.
Note that while it is easy to reduce Temp usage (shiutdown database, reduce value, startup database) reducing Perm is more complex (save all data and table defintiions, shutdown database, drop [destroy] database, reduce PermSize value, start up [new] database, re-create tables/cache groups/indexes etc., repopulate data).
Glad you have been able to improve things.