I have an application that repeatedly scans a table with about 60,000 rows
(no, I can't optimise this -- it's a telecoms app that doesn't use a simple
lookup). With about 3,000 users this kills the database server. The table
is static, and I access it using MTS, so I want to want to store the rows in
some sort of in-memory cache on the application server and scan them there.
The first instance of a component would load the data from the table and
initialise the cache; all instances thereafter would access the data from
the cache. The cache can remain in memory until the application server is
restarted.
But I don't know how to do it! :-) I thought that I could use MTS's Shared
Property Manager, but it stores only small data items. How can I create a
large-ish in-memory data structure, that can be accessed by all instances of
an MTS component?
--
Regards,
Greg Hawkes <rive...@iname.com.despam
(Remove ".despam" to reply, please)