Hello Ross,

Thanks for the prompt response. Assuming I'm not bothered about decoding and 
rendering part of incoming video (as I can offload that), I want to know if any 
profiling has been done on just LIVE555's receiving part on any processor ever?

I had observed in one of the experiments with OpenRTSP, if I periodically open 
multiple threads (using rtspRead()) to receive video streams from different 
sources, CPU load was going high. The application was just receiving and 
dropping packets. I want know measures that can be taken in live555 that would 
enable my system to open maximum possible threads/processes ensuring minimal 
overhead of receiving and waiting if any.

Regards,
Yogesh.

From: live-devel-boun...@ns.live555.com 
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Thursday, January 10, 2013 2:31 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Live555 performance numbers

I want to use live555 for receiving H.264 encoded video streams over IP network 
through RTP. Is there any information about performance numbers of live555 in 
terms of CPU cycles or CPU load % when it comes to receiving streams.

It's difficult, if not impossible, to answer questions like this, because the 
performance of the system depends so much on the particular hardware that 
you're using.

Generally speaking, though, the performance overhead of LIVE555's RTSP/RTP/RTCP 
reception/processing code is usually insignificant compared to the cost of 
receiving/decoding/rendering the incoming video.

E.g., I suggest that you run the VLC media player application, that uses the 
"LIVE555 Streaming Media" code as its RTSP/RTP/RTCP client, and which can 
receive and play H.264 video.

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

Reply via email to