Offload ThingSet processing to dedicated thread #103
Labels
Comments
martinjaeger
added a commit
that referenced
this issue
Aug 18, 2020
Depending on the amount of data nodes, calling ?rec caused a stack overflow. Larger stack memory solves the issue, for further improvement see also #103.
martinjaeger
added a commit
that referenced
this issue
Aug 18, 2020
Depending on the amount of data nodes, calling ?rec caused a stack overflow. Larger stack memory solves the issue, for further improvement see also #103.
martinjaeger
added a commit
that referenced
this issue
Oct 26, 2020
Depending on the amount of data nodes, calling ?rec caused a stack overflow. Larger stack memory solves the issue, for further improvement see also #103.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The processing of ThingSet requests that result in a large amount of returned data (e.g.
?confand?rec) requires considerable amount of RAM (around 1kB). Currently, each thread that processes ThingSet messages (serial, CAN at the moment, GSM, LoRa in future extensions) needs to reserve that amount of stack memory.Suggested improvement: Offload the processing into a dedicated processing thread that is called asynchronously from other threads that send and receive the data via comms interfaces.
The text was updated successfully, but these errors were encountered: