Disconnecting all the time causing other problems

There are currently 15 online users at the moment

i just noticed our server is on Singapore, SG 🤪

The server on SG is not a problem. The api on the server is easily overloaded (100MB to 700MB+ ram usage in 15 minutes) and not scaled properly.

Sometimes it’s happen to me, the app disconnect and connect some few seconds later. Or when I’m sending a message it disconnect too

Hey guys, @tahyaamir managed to improve CPU load by a lot. However, you still might see reconnecting to server messages, but the overall speed of community should be better.

Testing.... :)

Seems to work much faster :)

Huge thanks to @tahyaamir !! This speedup is excellent work !! Currently this seems to be very usable.

I don't notice any lags

and changing to other view loads fast

to other parts of community

Looks fine on my side! Sometimes my chat disconnects for 1 sec, but i blame my wifi! 😆

Hey guys, glad you feel the improvement. There will be still disconnecting/reconnecting message, but @tahyaamir is working on it.

I see reconnection sometimes when the server is busy. The error message says, "It looks like Vanila Community is very busy right now, please try again in a minute.", I need to dig deeper into this to make this more stable.

Unfortunately my eyes are not in good condition, but I think I will figure something within next week if I am in good health.

The marked area says it's much more stable right now. But even this stable has reconnection.

Thanks for your support. Please bear with me. :)

We are bearing with you Tahy , get rest ur eyes, and i need to do the same, cause i have foggy sight for last 4-5 days

I'm still getting these disconnects every minute or two consistently.

Yeah I'm facing the same problem since day 1 😞

sorry to hear that guys. Community is not perfectly deployed and that will happen in future once we release main projects, where main public communication will be here. So we will need it to be smooth for sure.

Hello community, We need the community for some real projects we have. So I was bound to look into this issue sooner or later.

Today, I was monitoring the community whole day related to this problem. It looks like there are two major points related to this problem.

First is the response time. The community api takes as long as 1 second (1000ms) to respond, which is a nightmare. Usually this should be kept at most 200-400ms.

Second is related to the first point, the websocket cannot keep alive more than 1 minute. It reconnects every minute depending on the region. https://i.imgur.com/mf2QP2J.png

We are supposed to re-deploy this with some tweaks and updates, then let everyone know what went wrong. If anyone can provide a helping hand, I'll be glad.

Oh, one more important point. I think second point above is a issue with nginx on the deployment related to proxy_connect_timeout.

@fahimmd @joshwcorbett I applied some tweaks, so let me know if the reconnection issue is a bit better or not.