it's a known issue, if you want to get actual speed, you have to
measure it through log-files or through ettercap via counting
submit_sm entries per second.
here is a small script i use sometimes to measure last 120 entries
(argument $1 is the filename):
#!/bin/sh
LAST=120
echo $1
grep 'throughput ([0-9][0-9]\+' $1 | grep -vi 'throughput (0.00' |
awk '{a[$1$2$3$4] = $0} END { for (x in a) { print a[x] }
}'|sort -n|tail -$LAST|
sed -r 's/.* \(([0-9]+).*/\1/' |
awk '{if(min==""){min=max=$1}; if($1>max) {max=$1}; if($1< min)
{min=$1}; total+=$1; count+=1} END { printf "MIN:%s MAX:%s MEAN:%s\n",
min, max, total/count}'
it's not ideal, but I hope you'll get the idea..
2013/11/11 Iain Dickason <[email protected]>:
> Does anyone have any thoughts on this? Currently we have a hack in place
> reading the log file to get the true submit_sm/dpu rate. We would be very
> keen to be able to get the true rate from Kannel direct.
>
> Thanks
>
> Iain
>
>
> On Tue, Oct 22, 2013 at 1:00 PM, Iain Dickason
> <[email protected]> wrote:
>>
>> Hi all,
>>
>> Is there any way to get Kannel to report the PDU rate rather than the
>> message rate via the status page (or other methods?).
>>
>> We send a number of multi-part messages which distorts the message/second
>> statistics. For example if we have a connection that we can send at 100m/s
>> and we send a batch of messages that are made up of 2 parts per message
>> Kannel will report that it is sending at 50m/s, but counting the submit_sm's
>> you can see that it is sending 100 submit_sm's per second.
>>
>> Thanks,
>>
>> Iain
>>
>
>
>
> --
>
> Iain Dickason
>
> MODICA GROUP
> DIGITAL MEDIA SOLUTIONS
>
> Follow us on Twitter: http://www.twitter.com/modicagroup
> Network Status page: http://status.modicagroup.com
>
>
> Phone: +64 4 498 6000
