Dynamic JDB Table Cache Refresh

DSauve

Legendary Poster
I've been doing some reading about a new feature in E1 9.1 Update 2 called "Dynamic JDB Table Cache Refresh". Just curious if anyone else has used this feature and/or if you have any suggestions on how best to use this (tips & tricks).

Thanks in advance!

Test: E1 9.1 Update 2, Win2012 R2, Oracle 11.2.0.4, TR 9.1.5.3, Weblogic 12.1.3, BI Publisher
 

Tom_Davidson

VIP Member
Cool. I will be using this on several financial tables around period end. One thing that is unclear to me is do I need to do it for each web instance? How about the ES cache?

Tom
 

altquark

Legendary Poster
This is actually really good functionality that has been bolted onto something that has been around in OneWorld forever. The F98613 table has been around since time immemorial - and by caching certain static tables into this list, you'll likely see some performance improvements in E1.

To answer Toms' question - the F98613 is a system table and is therefore across the entire system. So if you make a change, it'll affect ALL servers. Its not recommended to create multiple versions of this table by environment - it'll take more management, and could come up with strange issues...!

Now, since each of the Enterprise Server Kernels is running by environment (as is, we hope, your Web Instances) - then each will have its own "cache" version.

Cache should time-out eventually - which is now updated by the P99410 - so if an instance isn't being used, then the cache (and therefore, the utilized memory) will eventually clear up.

However, you definitely need to be careful WHAT you cache. If you cache tables that are actually frequently updated, you'll put extra load onto your system - and that extra load could be significantly more than the benefit of the caching provides. However, you should be able to judicially be able to identify what tables are updated frequently or not.
 
Top