We have an #Announcements category in which all our members are automatically subscribed to watch the first post. This allows us to schedule the publishing of posts in to that category on set times/dates. In turn, the announcement is then emailed to around 25k members. The problem we face is that…

[이미지] Richie: If I watch Sidekiq I can see the “Scheduled” counter racking up all the individual emails one by one, once it gets to around 20,000 it then moves them over to the “Enqueued” tab, and then they eventually start sending out. I timed it this evening. I scheduled a post to publish …

Shooting from the hip, Is it possible it’s an infrastructure load issue?

Perhaps? I genuinely don’t know :person_shrugging: The CPU spiked to around 44% on the server: [Screenshot 2025-09-18 at 22.17.08] And I use AWS SES for the SMTP.

There’s two things going on here: delay while email jobs are enqueued processing time for sending the actual email For the first, I’m not 100% confident on this but I think lowering email_time_window_mins means the notifications get queued sooner. Once the email jobs are scheduled, your sidekiq …

[이미지] supermathie: For the first, I’m not 100% confident on this but I think lowering email_time_window_mins means the notifications get queued sooner. I don’t know how the backend works in the finest detail, but the email_time_window_mins is just a delay setting before the first email goes o…

[이미지] TempAccount: What would be the recommended setting, obviously dependent on infrastructure capability? Could a high setting result in server issues in terms of load or other? “As many as the server can handle”. It’s 100% dependent on the OP’s server capacity - too many and it’ll slow t…

[이미지] supermathie: Once the email jobs are scheduled, your sidekiq workers are working through them one at a time. Bumping up the sidekiq workers (set DISCOURSE_SIDEKIQ_WORKERS up from 5 to 10, 15, or 20 depending on server capacity) means more jobs get processed at the same time, so the queue g…

[이미지] Richie: Can I just create that setting under the existing unicorn workers setting, then rebuild? Eg: expose: - “443:443” env: UNICORN_WORKERS: 8 DISCOURSE_SIDEKIQ_WORKERS: 7 Is it as simple as that? :thinking: Is anyone able to confirm this is the correct change to make to…

I believe yes, given a brief inquiry to the AI bot. [이미지] Set Environmental Variables Self-Hosting notebook_with_decorative_cover This is a how-to guide for setting up environmental variables in a self-hosted Discourse installation. person_raising_hand Requir…

Thanks @TempAccount Interestingly, DISCOURSE_SIDEKIQ_WORKERS only appears eleven times across the whole of meta: https://meta.discourse.org/search?q=%22DISCOURSE_SIDEKIQ_WORKERS%22%20order%3Alatest_topic …and one of those is in this topic :flushed_face:

이메일 알림을 더 빠르게 보낼 수 있는 방법이 있을까요?

제품 지원 자체 호스팅

supermathie (Michael Brown) 10월 3, 2025, 10:23오후 15

네, 맞습니다.

대부분의 설정은 이 방식으로 재정의할 수 있습니다. 기본값은 discourse_defaults.conf에서 가져옵니다.

글		댓글	조회수
How to set Email sending speed limit? Product Support	9	2382	12월 8, 2020
Large number of queued jobs Product Support	5	1684	7월 3, 2017
Send Emails immediately for new Post Product Support	3	814	1월 23, 2022
Throttle Digest Email Product Support activity-summary	2	543	3월 10, 2023
Discourse not sending Emails to All Users in mailing list mode Self-hosting	22	1516	4월 1, 2020

이메일 알림을 더 빠르게 보낼 수 있는 방법이 있을까요?

Related topics