Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi, For durable notify container we use replication, each notify container client need its own channel, the same as done for mirror target. If there are large amount of durable notify container per client we indeed expects higher cpu and memory consumption, in order to avoid it you can try to use the event session api and use same session to all listeners of same client as explained in:https://docs.gigaspaces.com/xap/10.2/dev-java/session-based-messaging-api.html We intend to do multiplex automatically for durable notification in future release.

Regards, Ester