A^3

Performance of set_qos and create_participant

Hello:

I have an application that loads a fairly extencive QoS.xml file and configures several DDS readers and writers. I'm trying to optimize the startup time of this application. After profiling I found that most of the start time (>80%) is spent in set_qos and create_participant methods. Together they take ~440ms.

Are there ways to improve the start time?

 

Thank you.

Organization:

One topic, many users

Hello:

This is a bit of a design question. All RTI examples I saw so far use the one-topic->one-type methodology. I suspect I can reuse the type on a different topics.

However, can I setup one topic and use it to publish more than one type?

 

Organization:
Subscribe to RSS - A^3