You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After analyzing applications whit and without PAPIFY configurations and enabling/disabling the monitoring, we have discovered a performance issue associated to the use of papify within SPiDER. The behaviour is the following one:
No monitoring configuration and papify flag in main.cpp 'false' --> 11.8 FPS
No monitoring configuration and papify flag in main.cpp 'true' --> 10.4 FPS
Monitoring configuration and papify flag main.cpp 'false' --> 11.8 FPS
Monitoring configuration and papify flag main.cpp 'true' --> 11.4 FPS
With these values, it seems that when SPiDER tries to use PAPIFY without any configuration it spends extra time looking for it unsuccessfully. The (logic) workaround of disabling PAPIFY if it is not used works, but maybe some improvements can be done internally to avoid this behaviour, because it is slowing down SPiDER applications.
The text was updated successfully, but these errors were encountered:
After analyzing applications whit and without PAPIFY configurations and enabling/disabling the monitoring, we have discovered a performance issue associated to the use of papify within SPiDER. The behaviour is the following one:
With these values, it seems that when SPiDER tries to use PAPIFY without any configuration it spends extra time looking for it unsuccessfully. The (logic) workaround of disabling PAPIFY if it is not used works, but maybe some improvements can be done internally to avoid this behaviour, because it is slowing down SPiDER applications.
The text was updated successfully, but these errors were encountered: