My Meteor App experiences a severe performance degradation when run behind the firewall of a certain french bank.
On looking at my server logs and APM, it appears that the client is calling all its current subscriptions afresh every 30 seconds or so (i.e. the function that is passed to
Meteor.publish is rerun. I suspect that the client then receives the complete data set of every subscription each time. Which makes it very slow and pretty unusable (according to the individual trying to use the app from within the bank).
I presume I am right in thinking that this would not be the symptom if Meteor is simply falling back on SockJS? And I am assuming this must be due to some sort of communications restriction implemented by the bank.
I am not able to either replicate this or diagnose it from within the bank, so I’m afraid my request for ideas (at this time) is only based on this rather sketchy description. But I’m hoping someone might have some insight even so?