Skip to content
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

Performance loss with PAPIFY disabled #13

Open
dmadronal opened this issue Jul 12, 2019 · 0 comments
Open

Performance loss with PAPIFY disabled #13

dmadronal opened this issue Jul 12, 2019 · 0 comments
Labels

Comments

@dmadronal
Copy link

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.

@dmadronal dmadronal added the bug label Jul 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant