The program creates a separate thread for listening to the socket. And it has been confirmed that the socket listener thread and the context are in two separate threads. The data reception period of the socket is 100ms, and the period in which the context is called to launch the image is about 300ms. The current situation is that every time the launch function is executed for image rendering, other threads of the program will be blocked and cannot be executed, including the socket thread cannot receive data normally. What is the solution to this problem?
Attempts have been made to put the context instance and the launch function call into separate child threads, but there is still no improvement. Also try to use the setCPUNumThreads() function in the context, even if the number of threads is changed to 1, the above blocking situation has not been improved. I hope to get everyone’s help, thank you!
Please always provide the following system configuration information when asking about OptiX issues:
OS version, installed GPU(s), VRAM amount, display driver version, OptiX major.minor.micro version, CUDA toolkit version used to generate the input PTX, host compiler version.
If you’re calling setCPUNumThreads() that means you’re using the OptiX high-level API, not OptiX Prime?
Is the listener thread waiting for any GPU event?