Transient objects in LRU space

edit

Hi Ester, Do you mean a performance impact on write or on read? If on read, could we eliminate a performance penalty by using a read modifier MEMORY_ONLY_SEARCH?

Background: we have some business logic running co-located in a LRU space. Now we want to extend this business logic, and an extension requires storing some transient space objects. We could store them in a separate ALL_IN_MEMORY space, but than transient objects will not be co-located with the business logic, causing performance penalty on each access.

For read MEMORY_ONLY_SEARCH will indeed help, but we will go to DB in write as well since we have to know if its write or update and send notification accordingly. Do you also use direct persistence in this space?

Why will GigaSpaces go to the DB on write at all, if this object type is annotated as transient, that is, @SpaceClass(persist=false) which is the whole point of this question?

And yes, the space is using direct persistence.

I was referring to write of the persistent objects. and the use of LRU.