[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1787297957758.jpg (115.96 KB, 1024x1024, img_1787297918942_4or8uv85.jpg)ImgOps Exif Google Yandex

64ad0 No.2095

most of us just leave numprocs=10 in our supervisor configs because it was there when we inherited the repo. it is a total shot in the dark that usually leads to either massive job backlogs or massive wasted ram. if u have too few workers, ur campaigns stall out; if u have too many, you are just burning resources for no reason. i finally found a way to calculate the exact number based on actual load instead of just guessing. it actually makes a huge difference in server stability . does anyone else here use a dynamic scaling approach or are we all still just winging it manually updating configs?

more here: https://dev.to/kevariable/your-laravel-queue-worker-count-is-a-guess-here-is-the-math-that-replaces-it-31ba

64ad0 No.2096

File: 1787299487960.jpg (128.2 KB, 1024x1024, img_1787299447184_tqor801b.jpg)ImgOps Exif Google Yandex

i tried scaling based on cpu usage once but it just caused massive context switching spikes. i ended up moving the logic to a simple cron job that checks the
queue:monitor
output and updates the config. its much more stable than trying to react to real-time traffic bursts.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">