I added similar handling on low memory as suggested, but I applied lower delay and lower low memory level.

I also changed mechanism of generation of PubSub notifications so that component will send them as they are created instead of adding them to a queue and sending them later in one batch.

Maybe we should consider other improvement to mechanism of handling low memory case, ie. we should try to generate notification only n times, and if for each time we get info about low memory then maybe we should drop generation of this notification? I would suggest adding this as it would protect us against case in which under very heavy traffic server will be using almost all memory which will lead to permanently blocking generation of notifications by PubSub Component which could block whole component. But then we may never generate notifications on very high memory usage.

I added similar handling on low memory as suggested, but I applied lower delay and lower low memory level.

I also changed mechanism of generation of PubSub notifications so that component will send them as they are created instead of adding them to a queue and sending them later in one batch.

Thank you, good work.

Maybe we should consider other improvement to mechanism of handling low memory case, ie. we should try to generate notification only n times, and if for each time we get info about low memory then maybe we should drop generation of this notification? I would suggest adding this as it would protect us against case in which under very heavy traffic server will be using almost all memory which will lead to permanently blocking generation of notifications by PubSub Component which could block whole component. But then we may never generate notifications on very high memory usage.

This is a good point but I do not think we have to really worry about this. If the service is permanently running at the memory limits the installation is kind of broken anyway. This is more a deployment issue rather then implementation.