Desired timeslice in seconds how to#
Desired timeslice in seconds serial#
Desired timeslice in seconds code#

Using normal loop processing serialEvent() can pull Serial data from the hardware to local storage for processing - that is called leaving loop each time - or on any delay() that calls yield() or if yield() is explicitly called - or calls could be made manually just to assure the buffers are emptied.ĭid some trivial tasks with threading to see it work - but i2c or other hardware getting pulled away without warning can have issues. Solving those issues takes different effort Threading can create as many issues as it can solve.

Desired timeslice in seconds code#

You can post issues on the github to the author is something could be clarified.Īs noted, the posting was two hours delayed - walked away with it written on an 'interrupting task'Īs noted 'Depending on the code in use this can be problematic or require care for certain devices'.

Desired timeslice in seconds how to#

Post above on how to set individual timeslices. The problem i was running into was putting all the i2c operations in a thread - but then during that time RTCM data and 10 hz NMEA data would overflow hardware buffers after a few minutes of operation.

This should certainly be included in the docs for threading! I would venture to guess many would assume that only the threads are actually threaded with a whole world of hurt on the main thread if not carefully considering all the effects. Depending on the code in use this can be problematic or require care for certain devices - some notes to this effect in the ReadMe IIRC. Using Threading involves the use of Interrupt execution of registered threads - when time is up, they stop in their tracks to cycle to the next thread. yield its remaining time to allow return to other Threads when not needed. Refer to the docs it seems each thread can be given a unique timeslice value. Once Threads are enabled - everything is 'a thread' - including loop, as only one thing can run at a time on the single CPU core.ĪFAIK by default all threads are given the same value for timeslice.

Executing a lay() should mean it won't run until 1 second has passed, or thread.yield() might be executed when an active thread wants to surrender the remainder of its timeslice because it has no 'work' to do.Įxample with 1 second delay on all threads doesn't give any feel for the desired use and where the questions come into play.Īlso a complete example is good for others to see and edit. If two threads each with 10ms timeslice each would run about 50 times per second, less over head for the context switch, and assuming each thread uses all of it allocated time slice. It can exit early if 'done' - but will be set idle as the next task is made active when the timeslice expires.Ī thread with a 10ms timeslice will run 'In Turn' depending on when all other threads are serviced based on the use of their timeslice. Only one task can be running at a time - it will run for the established time slice. Threads take turns on the CPU and are switched by the context_switch() function, written in assembly