| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Can anyone explain conceptually what a nodelet is and what the motivation is for using one? The documentation says that nodelets are "designed to provide a way to run multiple algorithms in the same process with zero copy transport between algorithms" but I don't understand what this really means.
Are nodelets just a way of making your nodes more efficient?
Thanks!
Like Augusto pointed out, regular nodes use TCP. This works fine for a lot of things.
But if you have multiple processes that need to use messages that contain large amounts of data (like images or point clouds) packaging the message, sending it, then unpacking it can take a bit of time. If the two processes are on the same computer, it is quicker to just send a pointer to that data rather than sending the data itself over TCP.
This only works for processes (aka nodelets) on the same computer though since a pointer for one computer doesn't make sense for another computer. Nodes on the other hand can work over networked computers since you're sending the actual data.
So nodelets don't make the processes quicker, but it is a quicker way to get information from one process to another. A good rule of thumb would be to always use nodes (because they are easier to use, and more flexible) unless you get in a situation where the message passing is too slow for your application and causing problems, then you would consider using nodelets.
Can we use it over Python and rospy? or it is compatible with C++?
Maybe something like this image could be useful :-)
To answer to your question:
Are nodelets just a way of making your nodes more efficient?
It really depends on how your nodes communicate each other, and the reason for that communication. Sorry for the "it depends", but without any clue about your issue, no one can tell you more than this :-)
Have a look also here http://wiki.ros.org/roscpp/Overview/P...
as far as I know (and remember), I used as source http://wiki.ros.org/ROS/Concepts and http://wiki.ros.org/nodelet and the linked address, which have been published before the book you're linking. maybe I am wrong, but I'm not used to copy from books ;-) (without any citation)
I recommend you don't use nodelet. If you're thinking of using it, you might want to first consider just launching two threads in a single node, instead of two nodes. I think you will probably find that easier than trying to understand the nodelet library.
omg... It is not the threads that saves the memory but the actual data. Nodelet uses much less data size and if you were to know anything about the memory management you would know that smaller data are closer to CPU (caches) and are executed faster in magnitude
Nodelet transfers less data than typical ROS nodes. It is not more efficient than two threads, though. If you have two threads, they can both share a reference to the same data, so there is no need to copy anything. This is a basic and common C++ technique. Nodelet is a more complicated way of doing the same thing.
Efficient = Faster = less memory usage. The whole goal of any low level programming language is to minimize the time required to access and write to the memory, that is the whole point... If the same two threads can read and write into the memory much faster it is the definition of efficiency
I totally agree with @Sebastian. ROS and its nodes actually make things more simple by wrapping them in simple forms. Nodelet is actually a form of thread in C++. If you are a professional in C++ then you don't have to spend time to read about a library which just wraps the library that you already know which is std::thread in this case.
Asked: 2016-04-04 14:35:55 -0600
Seen: 17,605 times
Last updated: Mar 31 '17
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
