Performance / how long it takes to send one message

[stilsch]

Hi!
Today I tested how fast the sending of a message is. Test was done on a linux with i5-4590T. Its somehow very slow compared to how fast sending via my android phone is. Is that normal? Do you know a way to speed this up?

--> json-rpc
time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "bla", "number": "+XXX", "recipients": [ "+XXX" ]}'
{"timestamp":"1677332755412"}
real	0m6,435s
user	0m0,005s
sys	0m0,022s

--> normal
time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "bla", "number": "+XXX", "recipients": [ "+XXX" ]}'
{"timestamp":"1677332876926"}
real	0m5,870s
user	0m0,008s
sys	0m0,015s

Regards,
Schuft

[bbernhard]

Usually the json-rpc mode performs way faster than the normal mode. Is sending a message in json-rpc mode only slow the first time you send a message, or always?

[vloschiavo]

+1 for the json-rpc mode. It's very fast for me, like sub-1 second.

[stilsch]

sorry for long-time-no-answer.
Sending always takes 5s+

with newest container (numbers changed for anonymity):

root@signal:~# docker run -d --name signalapi --restart=always -p 8080:8080 -v $HOME/config/signal-cli:/home/.local/share/signal-cli -e 'MODE=jason-rpc' -e 'AUTO_RECEIVE_SCHEDULE=0 22 * * *' bbernhard/signal-cli-rest-api

root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnaggg", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1684698957471"}
real	0m5.155s
user	0m0.000s
sys	0m0.009s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnaggg", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1684698964263"}
real	0m5.202s
user	0m0.005s
sys	0m0.004s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnaggg", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1684698971415"}
real	0m5.090s
user	0m0.006s
sys	0m0.003s

[kxait]

root@signal:~# docker run -d --name signalapi --restart=always -p 8080:8080 -v $HOME/config/signal-cli:/home/.local/share/signal-cli -e 'MODE=jason-rpc' -e 'AUTO_RECEIVE_SCHEDULE=0 22 * * *' bbernhard/signal-cli-rest-api

should be json-rpc, not jason-rpc, but I assume you fixed it already?
@stilsch

[stilsch]

I've tested again with latest version from docker container 0.70.
Outcome: json-rpc is now 10 times faster that native. With the downside that json-rpc maxes out my CPU (even while no messages are send) while with native no impact on CPU is visible. But that's as I understand a known behavior.

root@signal:~# docker run -d --name signalapi --restart=always -p 8080:8080       -v $HOME/config/signal-cli:/home/.local/share/signal-cli       -e 'MODE=native' -e 'AUTO_RECEIVE_SCHEDULE=0 22 * * *' bbernhard/signal-cli-rest-api
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnaggg", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187457887"}
real	0m2.459s
user	0m0.005s
sys	0m0.005s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnaggg", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187462119"}
real	0m2.074s
user	0m0.007s
sys	0m0.007s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassggg", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187472326"}
real	0m1.984s
user	0m0.000s
sys	0m0.008s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassggg", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187475567"}
real	0m1.955s
user	0m0.005s
sys	0m0.002s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassggg", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187483329"}
real	0m1.911s
user	0m0.008s
sys	0m0.000s


root@signal:~# docker run -d --name signalapi --restart=always -p 8080:8080       -v $HOME/config/signal-cli:/home/.local/share/signal-cli       -e 'MODE=json-rpc'  bbernhard/signal-cli-rest-api
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassgggpp", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187579741"}
real	0m0.210s
user	0m0.010s
sys	0m0.000s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassgggpp", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187581513"}
real	0m0.157s
user	0m0.008s
sys	0m0.000s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassgggpp", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187582702"}
real	0m0.150s
user	0m0.008s
sys	0m0.000s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassgggpp", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187583930"}
real	0m0.198s
user	0m0.008s
sys	0m0.000s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassgggpp", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187585395"}
real	0m0.159s
user	0m0.008s
sys	0m0.000s
root@signal:~# time curl -X POST -H "Content-Type: application/json" 'http://192.168.10.97:8080/v2/send'  -d '{"message": "nagnassgggpp", "number": "+1234", "recipients": [ "+4321" ]}'
{"timestamp":"1701187586562"}
real	0m0.170s
user	0m0.008s
sys	0m0.000s

So I would say - problem solved (unless anyone says my numbers are higher than usual). :-)