OE 11.7.17 (or whatever the latest patch is).
Redhat
We have a table in the database that is the system control table. Pretty much every program has an include file in it to read this record. Sometimes this even happens multiple times due to nested includes. It's a mess.
We are reading this table over 4000 x per second. Which is insane. It is mostly static data. If it does change then it is rarely. So it's a perfect candidate for caching.
Yes, I suppose it's persistently in the -B but it offends me that the churn is so high!!
This is a classic webspeed application. Requests are usually only to a single .p. So standard caching only removes the situations where the record is read multiple times in one program.
Does anyone have any ideas how I might go about caching this record for a predetermined period of time before re-reading it from the database?
Considerations should include that we will be moving to PASOE in the not too distant future.
Redhat
We have a table in the database that is the system control table. Pretty much every program has an include file in it to read this record. Sometimes this even happens multiple times due to nested includes. It's a mess.
We are reading this table over 4000 x per second. Which is insane. It is mostly static data. If it does change then it is rarely. So it's a perfect candidate for caching.
Yes, I suppose it's persistently in the -B but it offends me that the churn is so high!!
This is a classic webspeed application. Requests are usually only to a single .p. So standard caching only removes the situations where the record is read multiple times in one program.
Does anyone have any ideas how I might go about caching this record for a predetermined period of time before re-reading it from the database?
Considerations should include that we will be moving to PASOE in the not too distant future.