Hi Bala,
I don't know enough about the message processing in Asterisk to give
hints on that level.
I only wanted to indicate that it could be network transmission time
that sets the limit to the throughput for MESSAGE. There will be at
least 4 transmissions on SIP level, to share the 70
Hi Gunnar ,
Each message is addressed to unique and single URI and as expected
by protocol after receiving 202 for each message .
Then it is expected rate because the protocol requires end - to -
end confirmation by 200 OK or 202 before sending next MESSAGE.
[Bala] any
Hi Bala,
You did not answer my question:
Do you send these MESSAGE between the same two SIP URI:s?
Then it is expected rate because the protocol requires end - to - end
confirmation by 200 OK or 202 before sending next MESSAGE.
If you send to many URI:s, then expected throughput might be
On Mon, Jun 12, 2017 at 12:23 PM, bala murugan
wrote:
> Thanks Gunnar ,
>
> This is load test to understand how many message it can handle and where
> the bottleneck is .
>
> 14 MESSAGE / sec - takes longer time for the Message to be processed , not
> sure if there is some
Thanks Gunnar ,
This is load test to understand how many message it can handle and where
the bottleneck is .
14 MESSAGE / sec - takes longer time for the Message to be processed , not
sure if there is some kind of delay in picking up the message from the
queue
and also it will never be realtime
Den 2017-05-23 kl. 23:58, skrev bala murugan:
Hi ,
Is anyone aware of how many SIP MESSAGE per sec asterisk can handle ,
is there a benchmark
has this been load tested and results available some where , if there
is can you some one share it please .
The reason is we ran 16 per sec and we
Hi ,
Is anyone aware of how many SIP MESSAGE per sec asterisk can handle , is
there a benchmark
has this been load tested and results available some where , if there is
can you some one share it please .
The reason is we ran 16 per sec and we see the ast_msg_queue is backing up
with lot of