The RealSense SDK software has a couple of Known Issues related to CPU load that are being worked on. They should be fixed in subsequent versions of the SDK.
- CPU utilization increases with Projector switched off
- The Viewer and the visual examples CPU utilization is high, when streaming depth or color
Regarding the Viewer settings: unfortunately I was unable to locate documentation for them to meet your needs despite an extensive search. A member of the Intel support team may be able to confirm to you later whether such documentation for the Viewer settings exists yet.
Thank You, MartyG!
I am aware that there is still much work to be done, but the load on the processor when streaming RGB really surprised me.
Depth stream does not take nearly as much load as the RGB does, at least in my experience. Also, switching off the projector helps a little, but not nearly enough.
It remains to be seen how the things will evolve.
Thank You for the provided information!
You are very welcome!
If you are not already using SDK version 2.10.1 (the most recent release) then I would recommend trying that, as it contains a setting that disables the 'OpenMP compile flag' by default to reduce CPU load.
I'm very glad I could help.
I had another look through the source code of the Viewer's files in relation to its Advanced menu options but still could not find any notes to explain the functions. In the meantime, you may be interested in the documentation for custom calibrations of the camera.
2 of 2 people found this helpful
Another option that would give you some control over how many threads are used, is to re-enable openmp (-DBUILD_WITH_OPENMP=true) and then set either of the environment variables OMP_DYNAMIC (TRUE) or OMP_NUM_THREADS (to some value less than the number of cores/threads your system has). These variables can also be set in the code (e.g., omp_set_num_threads(2)).
Visual Studio references but I think they are same/similar on other platforms.