buddharide
Forum Replies Created
-
So I tried these steps and performance got slightly better:
1/ We raised the memory limit to 1024M (overall 3072M for the website including all PHP workers).
2/ We raised the max_execution time to 300 as requested.
3/ We’ve set the cron job to run every 3 minutes instead of every 30 minutes.
4/ I setup Multithreading
5/ Unfortunately my host only has one core unless I’m willing to pay a lot more $$.
So overall, a slight performance increase. I think my next step is to send over a timeframe. I’m certainly open to other recommendations.I created a PHP Snippet that when Status is Unsubscribed add tag Unsubscribed. Then I can create automations that use the tag. It’s not a perfect solution. It would be better if we could have an automation run when status change, instead of on cron run.
If you’re using this, change the number to whatever you use for your Unsubscribe tag and your cron frequency. Use the link below to access the PHP.
I’m considering making another for if status is Subscribed add a Subscribed tag, but I’m concerned what will happen with status changes. It’s not ideal that it happens only on cron, but It’s a functional workaround because you can add automations to tags.
- This reply was modified 11 months, 3 weeks ago by buddharide.
No solution yet, this is what I’m trying:
Enabled the multi-thread feature in FluentCRM? This feature allows FluentCRM to send multiple emails simultaneously, significantly improving the speed of bulk email campaigns. (settings>advanced feature config)i
Asked host to schedule every-minute cron job for FluentCRM? Setting up a server-level cron job that triggers every minute ensures smoother processing of your email batches.
Could my SMTP provider (Mailgun) has any limits on the number of emails I can send per minute or hour?Asked host to ensure your server’s PHP configuration supports long-running processes? Specifically, check the following settings and increase them if necessary:
- max_execution_time: Set this to at least 300 seconds (5 minutes).
- memory_limit: Increase this to at least 256M or higher.
Last thing I did was ask host to verify that the server was multi-cpu and 4gb memory min.
I’ll let you know if this resolves it.
Best,
Adam
The MacrodoseUpdate on this – the cron did not solve the issue. Does anyone else have this problem?
When you send emails – the site is unreachable for 10 mins or so, and no links work? If so what have you done to solve this?Hi Shahjahan Jewel.
I’m a FluentCRM Pro user and currently using Mailgun via the FluentSMTP + FluentCRM integration.
I’d love to request support for a powerful Mailgun feature that’s currently unavailable in the FluentCRM interface: Send Time Optimization (STO), which is triggered via the following custom header:
X-Mailgun-Delivery-Time-Optimize: yesThis header instructs Mailgun to automatically optimize the delivery time of each message based on recipient engagement history. It’s a valuable deliverability feature, especially for larger or more distributed audiences.
It would be amazing if FluentCRM allowed us to pass this header when sending via Mailgun API—either globally via settings, or as an optional toggle in the campaign editor.
This would:
- Improve deliverability for behavior-based sending
- Keep FluentCRM competitive with ESPs that already support STO
- Allow power users to take advantage of Mailgun’s full feature set without custom code or outside automations
There are a couple other features I would also like to request, but I’ll save those for another time.
Best,
themicrodose.ai