thread

Achieving low jitter and more deterministic write times and real-time performance requires in-depth tuning at the OS layer and DDS layer. It tends to involve a long list of recommendations to apply e.g. you can see advice online that involves similar checklists. This article summarizes best practices, and we recommend exploring and testing all the recommendations listed here. ...
4828 reads — 0 comments
Jitter when making API calls can result in inconsistent execution time for making those calls. For example, the median call to return_loan() may take ~4,500 nanoseconds, but there could be execution outliers that take 5-10x this median time. What could cause this kind of behavior? The cause of such ...
2858 reads — 0 comments
Note: This article applies to Connext DDS Professional 4.x and above. RTI Connext DDS Professional uses multiple internal threads for sending and receiving data, maintaining internal state, and calling user code when events occur. We recommend consulting the Connext User's Manual section ...
7143 reads — 1 comment
If the logic of your application requires to spawn new threads, and in those threads you are calling a DDS API such as write() , you may notice a memory growth. To ensure that all the resources allocated in that thread are correctly released, remember to call unregister_thread() right before ...
4149 reads — 0 comments
Not all API calls are safe. In general, the get / set_default_XXX_qos() and lookup_xxx() APIs are not thread-safe. The online HTML documentation for various API calls commonly include one or more MT Safety sections which describe any concerns about the use of individual calls in multi-threaded ...
4249 reads — 0 comments
Subscribe to RSS - thread