We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
step1: compile fastdds with -DFASTDDS_STATISTICS=ON(default is on)and -DPERFORMANCE_TESTS=ON step2: ./LatencyTest publisher -f payloads_demands.csv --domain 0 -s 1000000 ./LatencyTest subscriber -f payloads_demands.csv --domain 0 step3: configure fastddsmonitor to introspect FASTDDS LATENCY like picture1, but the graph is always empty.
The text was updated successfully, but these errors were encountered:
Hello, did you find a way to deal with this issue?
Sorry, something went wrong.
Is there any improvement on this topic? @wannastar @Jackie2chen
haha You can increase the number of FastDDS instances and ensure reliability to solve this issue.
I could not understand. Do I need to start 2-3 instance of latency process @Jackie2chen
No branches or pull requests
step1:
compile fastdds with -DFASTDDS_STATISTICS=ON(default is on)and -DPERFORMANCE_TESTS=ON
step2:
./LatencyTest publisher -f payloads_demands.csv --domain 0 -s 1000000
./LatencyTest subscriber -f payloads_demands.csv --domain 0
step3:
configure fastddsmonitor to introspect FASTDDS LATENCY like picture1, but the graph is always empty.
The text was updated successfully, but these errors were encountered: