otUDPnewMessage unable to allocate memory at faster rate #8272
-
Hello, I am using the Nordic mqtt-sn example as the base for developing my thread solution. So my Sleepy end device has two types of data collection modes:
Also in my example I haven't used any dynamic memory allocation function such as malloc and nrf_malloc (Nordic) etc. So I would like to know why my single node in the network is unable to publish at the rate of 100ms interval continuously . So I need continuous data instead of buffered data which will make graph look lagging. Hoping for a quick response. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
OpenThread maintains a message buffer pool for allocating messages (including UDP messages). The size of the message buffer pool is specified using the following build option: openthread/src/core/config/misc.h Line 170 in 9ebe41f If the offered load is less than what Thread can deliver, then you can try increasing the message buffer pool size. However, if the offered load is higher than what Thread can deliver, then you will need to rethink how many messages your application generates. |
Beta Was this translation helpful? Give feedback.
OpenThread maintains a message buffer pool for allocating messages (including UDP messages). The size of the message buffer pool is specified using the following build option:
openthread/src/core/config/misc.h
Line 170 in 9ebe41f
If the offered load is less than what Thread can deliver, then you can try increasing the message buffer pool size. However, if the offered load is higher than what Thread can deliver, then you will need to rethink how many messages your application generates.