Support forum
Unfortunately I am away from the office at the moment and not able to test things out. But a general recommendation is to keep the send log as small as possible. If the log database table gets too large, the database queries will take longer and longer long to process.
If the issue is mainly with the send log of the SQL Connector then it might help to increase the MaximumBatchSize value in the advanced settings of the SQL Connector. But this probably won't help if the database is already very large.
Regards, Henk
8:05 am
Hi Henk,
Thanks for your reply.
I wanted to mention that we are also experiencing this issue with the SMPP connector. When a user sends 50,000 SMS or more, the send log experiences significant delays before it begins inserting records into the SQL server log. Our server has 256GB of RAM, a W225 Xeon CPU at 3.00 GHz, and an NVME HDD.
Should we increase the message limit to 1000, or should we lower it to maintain the health of the connectors and avoid high delays in the send log?
Please advise.
Thanks,
Hello Adam,
The web application in Diafaan SMS Server is not really designed for bulk SMS. It is designed to provide a simple way to send SMS messages manually and view the received messages. By default the number of messages per user in the message log of the web is limited to 1000 messages. If you have increased that number, or if you have a large number of users, that might cause the delays.
Apart from the limit in the send log, or using a faster server, I can't think of any suggestions to increase the speed of the send log in the Web Connector.
Regards, Henk
6:22 pm
Hi Henk,
We have a .NET Core API gateway set up with four web connectors using round-robin load balancing. However, when any connector handles more than 50,000 SMS, messages continue to be sent to the gateway normally, but there is a significant delay in processing the send log. Sometimes, it takes over an hour for the messages to appear in the send log. This delay is causing issues for customers who cannot see their sent message logs promptly.
Do you have any suggestions on how we can resolve this issue? Any advice would be greatly appreciated.
Most Users Ever Online: 529
Currently Online:
2 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Member Stats:
Guest Posters: 681
Members: 0
Moderators: 0
Admins: 1
Forum Stats:
Groups: 2
Forums: 3
Topics: 1160
Posts: 3962
Newest Members:
, Henk HelmantelAdministrators: Henk Helmantel: 1518