[Live-devel] Live555 performance numbers

[Jeff Shanab]

Actually. As I re-read your question I see you asked about not writing, I do not have an answer for that as that is what my software does. Also, It is a 32 bit build so the process is only given the maximum 2G of address space, it just means other processes on that box are not impacting it's memory footprint. ( a good trick for isolating system load from app on windows, run 32bit process on 64bit os)
________________________________
From: live-devel-bounces at ns.live555.com [live-devel-bounces at ns.live555.com] on behalf of Jeff Shanab [jshanab at smartwire.com]
Sent: Friday, January 11, 2013 7:28 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Live555 performance numbers

 Oh, Sorry, Less than 25% CPU with the 400 streams. Leading me to believe I can handle a lot more on a rack server with multiple interfaces and a better upstream.
Indeed we now have over 500 cameras on a co-located dl380.

I would like to know what is the best way in such a situation to know when you get behind. Other than watching the video, I can check my index which gives me a frame count.
Is there a hook to tell me at the time live555 is forced to drop a frame in RTSP? or does it reconnect at that point.
________________________________
From: live-devel-bounces at ns.live555.com [live-devel-bounces at ns.live555.com] on behalf of Marathe, Yogesh [yogesh_marathe at ti.com]
Sent: Friday, January 11, 2013 1:03 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Live555 performance numbers

Jeff,

Thank you for your input. Is this the max performance on your system? Or CPU is still not fully loaded with 400 D1 at 10fps receive and write. It will be of a great help if you could comment on CPU performance when you are only receiving and not writing.

I will see if I can extrapolate these stats for my system. Unfortunately, I’m devoid of such processing power and memory you mentioned.

Regards,
Yogesh.

<snip>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130111/804cee15/attachment.html>