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
Currently, the simulator has an FPS option for updating the pipeline and displaying the results.
I'm suspecting we cap out somewhere from 30-60 FPS, which means our pipeline has a bottleneck somewhere.
The tasktaker should run a profiler on the code and see which areas are bottlenecks and start from there.
The most CPU intensive areas are probably the source info generation, which will likely get worse when we go into V3 of the multi module PVSource implementation.
The text was updated successfully, but these errors were encountered:
Currently, the simulator has an FPS option for updating the pipeline and displaying the results.
I'm suspecting we cap out somewhere from 30-60 FPS, which means our pipeline has a bottleneck somewhere.
The tasktaker should run a profiler on the code and see which areas are bottlenecks and start from there.
A tutorial to start you off: https://medium.com/@antoniomdk1/hpc-with-python-part-1-profiling-1dda4d172cdf
The most CPU intensive areas are probably the source info generation, which will likely get worse when we go into V3 of the multi module PVSource implementation.
The text was updated successfully, but these errors were encountered: