Faster sending?

[Carst Komdeur]

Hello,

So we sometimes send out 30.000 mails.
We do this with SparkPost. Which seems to work fine.

Unfortunately the sending process is very slow.
We work with 1 sending server. Which is SparkPost.
I can see some tips on the Knowledgebase and all settings seem to be correct.

Is there anyone who can give us some tips and maybe some screenshots of sending settings pages that can help us speed up the sending process?
Reading on the forum people get alott higher sending rate but ours is pretty low and will take ages to send out the 30.000 mails....not minutes but longer then a day.
The problem does not seem to be the server since we are using SparkPost, SparkPost says we can send alott faster then we do now.
So there must be someting wrong in our settings which causes this.

Any tips are welcome.

Edit:
I added screenshots of current settings. Hope this helps.

 

[twisted1919]

@Carst Komdeur - Try to debug the send-campaigns command to see where mailwizz spends it's most time:
https://kb.mailwizz.com/articles/debug-send-campaigns-command/

 

[Carst Komdeur]

@twisted1919
Thanks, I will look at this later today and report back.
Do the settings in screenshots seem normal / okay to you?

Thanks for your help!

 

[twisted1919]

@Carst Komdeur - They seem high to me.
1000 subscribers at once is a lot when you have 15 campaigns and 15 batches in parallel.
I'd go more with 300 subscribers at once, 5 campaigns in parallel and 30 subscriber batches in parallel.

 

[Carst Komdeur]

@twisted1919
Tanks, i will give this a try.

I must say that it will never happens we will use more then 3 campaigns at once, that is why we set the subscribers higher.

 

[twisted1919]

that is why we set the subscribers higher.

Yeah, but if you read https://kb.mailwizz.com/articles/un...ery-settings-and-how-they-impact-performance/ you will see that mailwizz works best with smaller batches but many of them.

 

[Carst Komdeur]

@twisted1919

Can you please also advice on settings like:
Emails per minute
Send at once
Pause

This week we send another batch out and will check with ssh if we can find out anything.
When all settings are changed we hope to see a better sending process.

Thanks for your help

 

[twisted1919]

@Carst Komdeur - Unfortunately there is no magic method which i could suggest since it depends on so many factors. best is to simply increase the sending settings gradually and see how they behave.
Remember, mailwizz performs better with lots of batches but small counts of subscribers at once.

 

[Carst Komdeur]

Hello again

We tried the debug send-campaigns command.
I added a small part of the log in the uploaded file.

To me it seems the connection to sparkpost isn't really quick and it takes at least 2 seconds for a mail to send.
Can you please look at this and confirm this or maybe have an idea of what else can go wrong?

Thanks in advance!

 

[twisted1919]

@Carst Komdeur - Please apply https://forum.mailwizz.com/threads/fix-for-slow-sending-speed-for-mailwizz-1-5-7.5128/

 

[Carst Komdeur]

Thanks!
We overwrited existing files. Will report back when a new batch has been send.

 

[Carst Komdeur]

Hello,

Overwriting the files did not solve the problem.
We are still sending with 20 / 30 mails per minute.

Any more tests we can do to find the cause or anything you can do to help us?
It costs us alott of time already with no solid solution. I hope you can help us solve the issues once and for all.

Thanks

 

[twisted1919]

@Carst Komdeur - You can open a ticket and include ssh access so we can debug it.
Also prepare a campaign for us so we have a way to test things.

 

[frm.mwz]

It costs us alott of time already with no solid solution.

This is why you are better off hiring an expert, if you want to save time.

I hope you can help us solve the issues once and for all.

In some situations, there is no other "solution" than to change the delivery server (DS), since some have only one global injection point and your server is located far away (i.e. huge ping time). If you are flexible, there is usually a way (e.g. DS change or move to another host close to your injection point).