Ruben, There is no "magic" rule or number that will give good results in all cases. It is totally dependent on your own application, and it's timing requirements. Your best bet is to actually do some profiling on your "heavy" operation and determine how long it actually takes on your specific hardware. If for example you have timers that perform important operations every 2 seconds(that cannot be delayed/skipped), you would probably want to break your heavy operation into chunks significantly less than 2 seconds. You can also do some profiling after implementing your heavy operation, and see how often you miss deadlines in your application. Knowing this can help you tweak how you break it up into sub-tasks.
Hope this helps, -Paul Ruben Rios wrote: > Hello everyone, > > I have been reading around about the problem of having computationally > heavy operations and decompossing such operations into lighter tasks. > But my question is, when should I do this? I mean, is there a rule of > thumb (such as loops over 50000 repetitions) to know when should I use > tasks ??? > > Thanks > > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
