Thank you for this article, very useful! I was wondering if you had a course or tutorial on how to configure horizon for let's say the GenerateReport use case, but having 100 of reports per day? I'm always tweaking my setup to handle horizon with an external scraper service, but haven't found the perfect setup yet :D.
DL
David Lun
✓ Link copied!
Could you clarify the question?
SH
Silvan Hagen
✓ Link copied!
Thank you for the quick reply and of course: I'm running a web app with horizon and sometimes have to handle large amounts of jobs which can be slow. It runs on a single server with 8 cores and 32 gb ram. So I would be interested in real-life examples of horizon/queue job configurations for handling 100-1000s of jobs per hour. My setup does work, but I would like to see other setups for bigger applications and what the best practices are for them. Of course only if that would be interesting for your audience.
DL
David Lun
✓ Link copied!
Well, I'd suggest identifying bottlenecks (is it memory? is it CPU?) first and scale accordingly to that. It is very situational.
DS
Dmytro Sakharuk
✓ Link copied!
The killer feature of Laravel Horizon is auto scaling workers!
Useful course, thank you!
Thank you for this article, very useful! I was wondering if you had a course or tutorial on how to configure horizon for let's say the GenerateReport use case, but having 100 of reports per day? I'm always tweaking my setup to handle horizon with an external scraper service, but haven't found the perfect setup yet :D.
Could you clarify the question?
Thank you for the quick reply and of course: I'm running a web app with horizon and sometimes have to handle large amounts of jobs which can be slow. It runs on a single server with 8 cores and 32 gb ram. So I would be interested in real-life examples of horizon/queue job configurations for handling 100-1000s of jobs per hour. My setup does work, but I would like to see other setups for bigger applications and what the best practices are for them. Of course only if that would be interesting for your audience.
Well, I'd suggest identifying bottlenecks (is it memory? is it CPU?) first and scale accordingly to that. It is very situational.