for me smsd needs around to 10 seconds to send one message (not-multipart) and much more for multipart messages.

it s ok?

sorry, I found answer - it is ok.
now I set "check_network = 0" and smsd work slightly faster.

other question: what is better AT+CPMS="ME","ME","ME" or AT+CPMS="SM","SM","SM"?
i think ME storage must be faster (and possible more reliable).

edo wrote

now I set "check_network = 0" and smsd work slightly faster.

If you move files to the outgoing directory (within the same partition), instead of creating and writing, you can speed up the sending with a setting trust_outgoing = yes. This will save one second more.

edo wrote

other question: what is better AT+CPMS="ME","ME","ME" or AT+CPMS="SM","SM","SM"?
i think ME storage must be faster (and possible more reliable).

I do not know whether the memories have a speed difference in practice. It has never been an issue.

With a large number of messages, the setting check_memory_method with a value 31, 41 or 5 will speed up the receiving. This setting depends on the modem.

keke wrote

If you move files to the outgoing directory (within the same partition), instead of creating and writing, you can speed up the sending with a setting trust_outgoing = yes. This will save one second more.

1. with this setting I get message:
smsd: Setting trust_outgoing cannot be used with small setups (less than 10 modems).

2. this setting affects the movemment from 'outgoing' directory to 'cheked'?
then it has effect with only message in queue (for this modem): during rush hour in 'checked' will be several messages and outogoing-to-checked delay is unimportant.

3. IMHO message building in spool directory (and wait-and-check logic in smstools) is a bad think.

edo wrote

keke wrote

If you move files to the outgoing directory (within the same partition), instead of creating and writing, you can speed up the sending with a setting trust_outgoing = yes. This will save one second more.

1. with this setting I get message:
smsd: Setting trust_outgoing cannot be used with small setups (less than 10 modems).

[ Select ]

Sorry, I forgot that...

With less than 10 modems the mainspooler can easily keep the spooler filled up, even with a 1 second delay for each message file.

edo wrote

2. this setting affects the movemment from 'outgoing' directory to 'cheked'?
then it has effect with only message in queue (for this modem): during rush hour in 'checked' will be several messages and outogoing-to-checked delay is unimportant.

Currently this setting affects for both (all) directories. However, if smsd makes a spooling, as it usually does, the delay is not necessary for the modem processes. The next version will have a different setting for modems, trust_spool. I think that this setting could default to yes. However, care should be taken if some other process creates files directly into the spool directories, or if the checkhandler makes a spooling (during the load balancing).

edo wrote

3. IMHO message building in spool directory (and wait-and-check logic in smstools) is a bad think.

The wait-and-check logic has been there about ten years, starting from the 1.x and is an "original design". I also believe that this kind of checking is required, because there is no "good" locking mechanism for files in all supported platforms. And some people and applications build messages in spool directory, even if it's a bad think...

Usually this delay has not been a problem, but of course with very large number of messages the delay is remarkable. I think that the next version will be slightly better with this (trust_spool = yes).

keke wrote

However, if smsd makes a spooling, as it usually does, the delay is not necessary for the modem processes. The next version will have a different setting for modems, trust_spool.

it looks reasonable.