openRTSP create a new BasicUsageEnvironment to handle command line specified RTSP, but from source code, it seems that single BasicUsageEnvironment can handle multiple RTSP connections? Is there anyone have tried it?
We want to use live555 for a environment to manage more that 100 video streams through RTSP on 4 CPU core, if we use one thread for a RTSP connection thread schedule will use too much CPU time; and the current implementation is to modified select() to no wait, and create our scheduler to scheduler multi-BasicUsageEnvironment, but from profiling, select() for single RTSP/RTP used two much CPU time, and if we wait for all the socket, then check every envir then it got more performance. But that change is just a test and very hard to merge into live555's structure. So, is there any better solution? -- Cyberman Wu _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
