If you're not going to remove the data in the global in cachetemp, it is going to get written to disk as it will grow too big to keep in the buffer pool. cachetemp is useful for temporary globals which get built up and killed as the kill frees the space in memory to be used for something else.
In any case, why do you think you need something like this? When you set a global you're doing the set into memory and then occasionally the system writes your changes to disk. "Ed de Moel" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Set these values into an in-memory global variable > and have a background process that copies that one > to a global variable on disk every so many minutes? > > (Global variables in the database CACHETEMP reside in memory.) > > Ed > > Michael Kauflin wrote: > > hi > > > > i am writing my diploma thesis with java and cach�. i have to extend > > performance critical middleware; it sends messages to the connected > > editors via a server socket. there is one such middleware per database > > (so far), it has an ip-address and a port it listens to (they were hard > > coded so far, i made these values configurable). > > these values are needed every time a change in the database occurs (can > > be a very large number per second...). so far i set these values as > > globals. > > > > now my question: is there a way to set these values in the memory of the > > database from the java-based middleware (via object script and the java > > stubs)? and if yes how do i get these in order to send the messages > > correctly? > > > > thank you for your help > > michael >
