You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2020/06/04 14:09:38 UTC

[GitHub] [mynewt-nimble] haukepetersen commented on issue #818: L2CAP COC: link throughput inconsistent and fluctuating

haukepetersen commented on issue #818:
URL: https://github.com/apache/mynewt-nimble/issues/818#issuecomment-638873496


   Update: I still cannot specifically explain the throughput fluctuation. However, I was able to find a fix to get a stable throughput. Per default, the `MYNEWT_VAL_ACL_BUF_COUNT` variable for the RIOT port was set to `4`. Simply setting this to `5` (or any larger value) leads to a stable throughput of around ~62kb/s. 
   
   The issue above seems to be closely related to the value of `MYNEWT_VAL_ACL_BUF_COUNT`. If this value is too small, the throughput will decrease significantly:
   `MYNEWT_VAL_ACL_BUF_COUNT` := 1 --> ~2kb/s
   `MYNEWT_VAL_ACL_BUF_COUNT` := 2 --> ~4kb/s
   `MYNEWT_VAL_ACL_BUF_COUNT` := 3 --> ~6kb/s
   `MYNEWT_VAL_ACL_BUF_COUNT` := 4 --> ~8kb/s **BUT with temporary peaks to ~65kb/s**
   `MYNEWT_VAL_ACL_BUF_COUNT` >= 5 --> ~65kb/s
   
   So the question remains: why does the thoughput for `MYNEWT_VAL_ACL_BUF_COUNT := 4` fluctuate between slow and fast mode?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org