search

seomoz / qless

Queue / Pipeline Management
MIT License
294 stars 76 forks source link

Web App uses ~40 connections for a single request?? #287

Open stephenreay opened 3 years ago

stephenreay commented 3 years ago

We're using Qless in a non-ruby app, but we do use the ruby Web App for visibility of queue operations.

Today, after we had an event that produced a larger-than-normal load of jobs to be queued (i.e. the completed queue is now truncated at the last 50K), I notice the web app is either very slow to respond, or crashes with an error about connection being reset.

So I went into Redis, and monitored the client stats. Our regular application (which also uses redis for session data), plus our regular Qless workers mean we have a fairly stable connection count of around 70. Every time I try to load the Qless web UI, it jumps by about 40.

Regardless of these being pretty pedestrian numbers compared to Redis' own internal client limits: it doesn't seem at all normal to me that a single request to the Web UI would create 40 connections to the Redis server.

Is this something we can tune via environment variables or a config option?

dlecocq commented 3 years ago

Although it has been a while since I've used the webapp, that does seem wrong and not in line with my memory of how it would typically behave. Off hand I don't know of any setting or environment variable to adjust that :-/