InCrescendo

InCrescendo

Member Since 1 Month Ago

Experience Points
60
Total
Experience

4,940 experience to go until the next level!

In case you were wondering, you earn Laracasts experience when you:

  • Complete a lesson — 100pts
  • Create a forum thread — 50pts
  • Reply to a thread — 10pts
  • Leave a reply that is liked — 50pts
  • Receive a "Best Reply" award — 500pts
Lessons Completed
0
Lessons
Completed
Best Reply Awards
0
Best Reply
Awards
  • start-engines Created with Sketch.

    Start Your Engines

    Earned once you have completed your first Laracasts lesson.

  • first-thousand Created with Sketch.

    First Thousand

    Earned once you have earned your first 1000 experience points.

  • 1-year Created with Sketch.

    One Year Member

    Earned when you have been with Laracasts for 1 year.

  • 2-years Created with Sketch.

    Two Year Member

    Earned when you have been with Laracasts for 2 years.

  • 3-years Created with Sketch.

    Three Year Member

    Earned when you have been with Laracasts for 3 years.

  • 4-years Created with Sketch.

    Four Year Member

    Earned when you have been with Laracasts for 4 years.

  • 5-years Created with Sketch.

    Five Year Member

    Earned when you have been with Laracasts for 5 years.

  • school-session Created with Sketch.

    School In Session

    Earned when at least one Laracasts series has been fully completed.

  • welcome-newcomer Created with Sketch.

    Welcome To The Community

    Earned after your first post on the Laracasts forum.

  • full-time-student Created with Sketch.

    Full Time Learner

    Earned once 100 Laracasts lessons have been completed.

  • pay-it-forward Created with Sketch.

    Pay It Forward

    Earned once you receive your first "Best Reply" award on the Laracasts forum.

  • subscriber-token Created with Sketch.

    Subscriber

    Earned if you are a paying Laracasts subscriber.

  • lifer-token Created with Sketch.

    Lifer

    Earned if you have a lifetime subscription to Laracasts.

  • lara-evanghelist Created with Sketch.

    Laracasts Evangelist

    Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.

  • chatty-cathy Created with Sketch.

    Chatty Cathy

    Earned once you have achieved 500 forum replies.

  • lara-veteran Created with Sketch.

    Laracasts Veteran

    Earned once your experience points passes 100,000.

  • 10k-strong Created with Sketch.

    Ten Thousand Strong

    Earned once your experience points hits 10,000.

  • lara-master Created with Sketch.

    Laracasts Master

    Earned once 1000 Laracasts lessons have been completed.

  • laracasts-tutor Created with Sketch.

    Laracasts Tutor

    Earned once your "Best Reply" award count is 100 or more.

  • laracasts-sensei Created with Sketch.

    Laracasts Sensei

    Earned once your experience points passes 1 million.

  • top-50 Created with Sketch.

    Top 50

    Earned once your experience points ranks in the top 50 of all Laracasts users.

Level 1
60 XP
Nov
27
1 month ago
Activity icon

Replied to Kill Horizon Single Process After X Jobs

@bobbybouwmann processes timing that goes from 0.1 to 5 isn't so weird in some scenario, unfortunately, I already worked with them in other apps (a Symfony, it's not something related to Laravel). The queue I am talking about sometimes processes millions of messages per hour.

Thing is PHP is not so good for long-running processes. In the long run, performance decay is inevitable. In the previous app, I found my perfect tradeoff by giving each process a certain number of jobs to process before the shutdown.

I could do it manually with the work command for sure, but I would need to go outside Horizon. It seems that the current Horizon implementation gives me the possibility to define a "timeout" and a "sleep" options. However, sleep defines how much time the process must wait if no jobs are available before going down. But if jobs keep coming, nothing shuts down the process.

I tried to implement the most common solution (horizon:terminate after 10 minutes to "refresh" everything) but it's not enough. I will need a more granular control :D

If anyone has an idea about how to proceed with Horizon, it's welcome! Thanks for your answer

Nov
26
1 month ago
Activity icon

Started a new Conversation Kill Horizon Single Process After X Jobs

Hi,

I am working with Horizon, and I have a problem. Due to the PHP way of working with long-running processes, I stumble upon some performance issues with some queues processing.

When I start my consumers, jobs in these queues are processed in ~0.1s. After 10 minutes, runtime skyrockets to 5s.

Is it possible to specify to kill a specific horizon process after it processes, let's say, ten jobs?

Thanks a lot!