@maxime-petit and I have observed that changing the yarpserver to run on a desktop machine rather than the ikart improves the speed of yarp considerably. For example, in yarpmanager, refreshing the status of modules takes a couple of seconds when running yarpserver on ikart. Doing the same refresh with another server, it is much, much faster.
Also, when connections are made within modules, we observe the same behavior. Some of our WYSIWYD modules create quite a few connections at startup, and it took a couple of seconds before some of these modules started using ikart as yarpserver. Now, the modules start rapidly.
I don't think it makes sense investigating why this issue happens, but this is more meant as a hint for other people using the ikart that changing the nameserver might improve the performance of yarp considerably.
Hi all,
@maxime-petit and I have observed that changing the
yarpserverto run on a desktop machine rather than theikartimproves the speed ofyarpconsiderably. For example, inyarpmanager, refreshing the status of modules takes a couple of seconds when runningyarpserveronikart. Doing the same refresh with another server, it is much, much faster. Also, when connections are made within modules, we observe the same behavior. Some of our WYSIWYD modules create quite a few connections at startup, and it took a couple of seconds before some of these modules started usingikartasyarpserver. Now, the modules start rapidly.I don't think it makes sense investigating why this issue happens, but this is more meant as a hint for other people using the
ikartthat changing the nameserver might improve the performance ofyarpconsiderably.Best, Tobias