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

Durable Notifications CPU spike

Hi,

I recently enabled Durable Notifications and saw some CPU spikes leading to PUs becoming unresponsive and then being restarted.

I enabled durable notifications by calling .durable(true) on the SimpleNotifyContainerConfigurer when creating a NotifyContainer.

How much of a performance hit can Durable Notifications cause? How many extra resources would be required? I can't see any guidance in the docs around this.

Thanks, John.

asked 2017-08-24 04:43:37 -0500

jmg
15 ●10 ●13 ●16

updated 2017-08-24 04:49:49 -0500

edit retag flag offensive close merge delete

Comments

This was on 10.2.0

jmg ( 2017-08-24 05:23:45 -0500 )edit

add a comment

1 Answer

Sort by » oldest newest most voted

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

answered 2017-08-27 07:50:54 -0500

Ester
281 ●3 ●3

edit flag offensive delete link

Comments

Thanks very much for the response. I'll investigate the EventSession approach.

jmg ( 2017-08-28 05:03:04 -0500 )edit

add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2017-08-24 04:43:37 -0500

Seen: 2,938 times

Last updated: Aug 27 '17

Durable Notifications CPU spike edit

Comments

1 Answer

Comments