-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
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
takes too long to start up / refresh #3
Comments
From @ablasdel on August 16, 2013 15:16 I'll take a look at this later today. |
From @ablasdel on August 16, 2013 18:5 This is due to the python interface to rosservice not having an "exists" speed/convenience function like the cpp implementation. For this reason rqt_logger_level is forced to iterate over the existing services on each node in existence to see if it has "set_logger_levels". |
Since the issue is not resolved and still a problem the ticket should not be closed. If you don't see a way to fix it you could mark it with the milestone "untargeted" and comment why it can not be fixed earlier. If you would really close it you should mark it with the label "wontfix". In this specific case it might be most reasonable to figure out if that missing "exists" you mentioned is feasible to be implemented and would actually fix the prroblem. |
From @ablasdel on August 16, 2013 19:25 Then taking a step back and verifying it actually happens would be the next step. (I jumped to the possible culprits stage) |
From @tkruse on August 16, 2013 10:10
On my machine, with a reasonable number of nodes running on a remote PR2, rxloggerlevel takes about 6 seconds too start, rqt_logger_level about 12. Similarly a refresh in rxloggerlevel takes 3 secs, rqt_loggerlevel 12 again.
Since they do roughly the same, I assume that is a bug in rqt_loggerlevel. Probably you won't notice if the nodes are running locally or just a few nodes.
Copied from original issue: ros-visualization/rqt_common_plugins#147
The text was updated successfully, but these errors were encountered: