Gazebo | Ignition | Community
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Way to avoid gazebo calling gettimofday so much?

After having performance problems I ran sysprof along side gazebo and noticed that > 20% of the cpu resources being used up were for calls to sys_clock_gettime via gettimeofday via gazebo::common::Time::GetWallTime()

This seems unusual. Is this an indication that I've something mis-configured? Is there a way to mitigate this?

Way to avoid gazebo calling gettimofday so much?

After having performance problems I ran sysprof along side gazebo and noticed that > 20% 40% of the cpu resources being used up were for calls to sys_clock_gettime sys_clock_gettime() via gettimeofday gettimeofday() via gazebo::common::Time::GetWallTime()

This seems unusual. Is this an indication that I've something mis-configured? Is there a way to mitigate this?

Way to avoid gazebo calling gettimofday so much?

After having performance problems I ran sysprof along side gazebo and noticed that > 40% of the cpu resources being used up were for calls to sys_clock_gettime() via gettimeofday() via gazebo::common::Time::GetWallTime()

This seems unusual. Is this an indication that I've something mis-configured? Is there a way to mitigate this?

gazebo-1.2.6

Way to avoid gazebo calling gettimofday gettimeofday so much?

After having performance problems I ran sysprof along side gazebo and noticed that > 40% of the cpu resources being used up were for calls to sys_clock_gettime() via gettimeofday() via gazebo::common::Time::GetWallTime()

This seems unusual. Is this an indication that I've something mis-configured? Is there a way to mitigate this?

gazebo-1.2.6