Recommended stack & buffer sizes for LWIP and MQTT when using mesh_lite + MQTT (AEGHB-1106)

[BR-Coding-cmd]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate.
• Provided a clear description of your suggestion.
• Included any relevant context or examples.

Issue or Suggestion Description

Hi all,

Doing some research into the stack sizes of each node within a mesh and after some digging I've not seen much - mind you it's not something that a lot of people may have documented outside of using the previous version "ESP_WiFI_MESH"

Example use case:

Mesh size is 100 (maximum size for mesh_lite)
Each node sends out a packet of ~300 Bytes via MQTT every 10 seconds with a qos of 1

By the time we get to the master the amount of data could block other processes as the amount of messages to be handled along with other background tasks could result in a cascaded mesh failure - the mesh breaking apart (if I'm not mistaken)

Any suggestions and places for me to look and understand I'd be grateful

Thanks
BR

[BR-Coding-cmd]

For those, who may be looking for info about this. I've found this document/white paper, which discusses the increase of the LWIP stack and params (see fig 19)

https://dspace.ut.ee/server/api/core/bitstreams/a548d8b3-f4c7-461c-906a-f6f493a47f5d/content

Hope this helps others experiencing similar issues.

I'm currently testing this and trying to gauge the benefits and performances of the changes suggested

NB: it's worth noting that the way the system in the paper was set up was done with static master with an allowed level being set and the child nodes being left be.