Multiple instances of Horizon all connecting to single "use" Horizon configuration #57097
Unanswered
sts-ryan-holton
asked this question in
Q&A
Replies: 1 comment
-
We have setup multiple separate horizon instances with each their own cache. You just need different endpoints to access the dashboard that belongs to that instance. All instances including web knows about each other's caches and can dispatch jobs to the correct connection, back and forth. You would have for example a slow-job worker (horizon) and a fast job worker both as fully separate cache-horizon combination. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi 👋
Looking to gain some insights here. I'm currently running a large scale web application using Laravel Horizon. We're processing in the region of 30 million combined queued jobs per hour and have already gone to efforts to split out Horizon queues into different Redis instances, which has helped.
The issue though, is that Laravel Horizon utilises whatever the "default" connection is to store meta information to function, and we're seeing bottlenecks in the number of connections:
Was wondering how we can get around this? Is there anyway to distribute the meta information across Horizon instances whilst maintaining data integrity. Our current Horizon config looks like:
Beta Was this translation helpful? Give feedback.
All reactions