Peak connection in mysql logs incorrect

[lovetoast]

Rather strange issue!

I have about 20 connections online according to the API, but according to the mysql logs I have 180 peak connections!

Any ideas?

Thanks in advance and for the great package.

[rennokki]

The MySQL peak connections have nothing to do with the peak connections that this package store.

[lovetoast]

Hi Rennokki,

Thanks for your message, sorry for the delay. So I checked the number of open files for the supervisor processor, and that equates to the number of max connections. However, we have some clients which have 54 connections open, when they only have 1 tab open, on one computer and the connection code is only called once?

Not sure if you could shed some light of this?

[rennokki]

When you're calling new Echo() it counts as a connection. The deal is that you need only one alive connection to the server on which you communicate which channels you want the user to subscribe to & etc.

[lovetoast]

In our code, we only have one instance of pusher subscribe though?

[rennokki]

@lovetoast The package version you're using? We have fixed some memory leaks in 2.x (beta for now): #475

[lovetoast]

Ah right, I'll check this and revert back, it could also be a quick in how window.load works but I'll let you know as it may help others :)

[lovetoast]

@rennokki
Hi, as promised, I've been monitoring, using version 1.4.1. We use laravel websockets in document.ready, and there does seem to be an issue with multiple connections made from the same client. I don't think this is a memory leak, but I can see one person, with just 1 browser and 1 tab open and they have 54 connections, as mentioned, using pusher.js.

I'm not sure if an upgrade would fix this?