Re: [sr-dev] issue using evapi module with evapi_relay

Hello, tcp is a streaming protocol, it is the receiving application that has to parse and split the stream content in logical messages from its point of view. As you noticed, there can be socket options to enforce some sending policy (wait or not wait for a specific amount of data to accumulate, not to send too many small packets, but if it is too much in very short time, it is no difference). As a side note, your patch below is setting the TCP_NODELAY to listen socket, not to the socket associated with the client connection (returned by accept()). I do not think is inherited by accept() from listen socket, in such case practically your patch didn't make any difference in behaviour. The evapi module has the option (modparam) to serialize the packets in netstring format, being easier to split the stream in messages and I would recommend that mode for heavy traffic. At the end, we can introduce modparams for evapi to set TCP_NODELAY, it can be useful to reduce delays when sending short data messages from time to time, but it won't help in your case. Cheers, Daniel On 11.12.20 09:39, David Escartin wrote: Dear all seems the issue was not on the module or related to kamailio, but related to the application we were using to read from tcp socket. I saw that some messages sent with evapi_relay were encapsulated in the same frame, and i even tried to force the TCP_NODELAY option on the evapi socket by compiling the kamailio with this --- a/src/modules/evapi/evapi_dispatch.c +++ b/src/modules/evapi/evapi_dispatch.c @@ -30,8 +30,8 @@ #include <netinet/in.h> #include <arpa/inet.h> #include <fcntl.h> - #include <ev.h> +#include <netinet/tcp.h> #include "../../core/sr_module.h" #include "../../core/dprint.h" @@ -690,6 +691,15 @@ int evapi_run_dispatcher(char *laddr, int lport) freeaddrinfo(ai_res); return -1; } + + if(setsockopt(evapi_srv_sock, IPPROTO_TCP, TCP_NODELAY, + &yes_true, sizeof(int)) < 0) { + LM_INFO("cannot set TCP_NODELAY option on descriptor\n"); + close(evapi_srv_sock); + freeaddrinfo(ai_res); + return -1; + } + if (bind(evapi_srv_sock, ai_res->ai_addr, ai_res->ai_addrlen) < 0) { LM_ERR("cannot bind to local address and port [%s:%d]\n", laddr, lport); and i saw that with this change we had always a frame for each message published to evapi, but the issue was still there. So no matter if this option was activated or not in Kamailio, I had to tune the application (in erlang) to delimit the messages received by converting them to line mode. This way we could reach up to 1000 processed messages per second. best regards david El lun, 30 nov 2020 a las 11:19, David Escartin (&lt;descartin(a)sonoc.io&gt;) escribió: -- [image: Logo] David Escartín Almudévar VoIP/Switch Engineer descartin(a)sonoc.io *SONOC* C/ Josefa Amar y Borbón, 10, 4ª · 50001 Zaragoza, España Tlf: +34 917019888 · www.sonoc.io _______________________________________________ Kamailio (SER) - Development Mailing Listsr-dev@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev -- Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla