How to increase processing speed for custom channel deliveries | Community
Skip to main content
A
Annie19
New Member
September 22, 2022
Question

How to increase processing speed for custom channel deliveries

  • September 22, 2022
  • 1 reply
  • 1449 views

Hello,

 

We have a custom build inApp channel which is running based on JS connector. The deliveries are running fine for small volume but when we have to process like 100,000+ records, the processing speed goes really slow and it has hours and hours to finish running.

 

Any idea on the ways to improve the processing speed of custom channel deliveries running on MTA?

 

 

BR,

Annie.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

CedricRey
CedricRey
Level 5
September 29, 2022

Hi @annie19 

We had this issue last week, so the answer is very easy :

By default, processDeliveryPart gets 8 messages each call. This can be configured, but it is not a server paramareter. It's a delivery parameter : Delivery additional parameters, then Delivery tab, and Message batch quantity. This value is 0 to default, meaning 8 minimum. You can change this (and it can be over 256, we put 1000) if you need to process much more messages each call.

 

Cedric

A
Annie19Author
New Member
September 30, 2022

Hi @cedricrey,

 

Also, to understand, when you are executing a batchsize of 1000, have you experienced any slowness in the delivery processing speed? or does it goes out with the same speed as like an email channel?

 

Thanks in advance,

Annie.

CedricRey
CedricRey
Level 5
October 4, 2022

Hi @annie19 

We used custom connector for special channel, it use external API, requesting HTTP endpoint. So for us, processing 1000 messages at a time instead of 8 increased the speed considerably.

 

It depends of what you are doing in your connector, but you can see if anything is wrong with the logs : in the {install_dir}/nl6/var/{yourInstanceName}/logs/mtachilds.log, you should detect something thaht goes wrong during the process. You should take a look at this file.

 

Cedric

Terms & ConditionsAccessibility statement

Loading footer...