Test results: 1. core usage goes up to 100% when there are 10 concurrent connections, the usage might drop to normal level (about 1% or 2%) after few minutes passed. (sometimes it doesn't drop at all) 2. core usage goes up to 100% when there are 11 concurrent connections, the usage keeps 100% at all time. 3. according to procdump, the core usage is mostly consumed by method BasicTaskScheduler::SingleStep.
2013/7/12 Ross Finlayson <finlay...@live555.com> > I do modify the macro FD_SETSIZE=1024, but the situation is still the > same. > > > Once again, does your problem occur *only* when you have a large number of > concurrent client connections (e.g., 32 or more), and *not* when you have a > small number of connections (e.g., 5)? If so, then the problem is almost > certainly caused by you running into an OS-imposed limit on the number of > open files (sockets) that can be used by a single process. I *thought* > that changing "FD_SETSIZE" is the way to increase this limit in WIndows, > but I'm not a Windows expert, so I could be wrong about the solution. > > > Ross Finlayson > Live Networks, Inc. > http://www.live555.com/ > > > _______________________________________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/mailman/listinfo/live-devel > >
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
