[Live-devel] Correct use of 'select' to avoid packet loss in Linux+BSD; correct use of WSAGetLastError and codes

[Stas Desyatnlkov]

I can't share the code as it is part of the classified project. But its all really simple. 
1) Create N async sockets
2) Run a thread that will poll on the sockets once in say 50ms
3) Read all data available from all the sockets

The live555 lib is designed to be OS independent so running thread is not something it should do. 

-----Original Message-----
From: live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Marco Amadori
Sent: Friday, April 17, 2009 10:04 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Correct use of 'select' to avoid packet loss in Linux+BSD; correct use of WSAGetLastError and codes

On Thursday 16 April 2009, 09:41:53, Stas Desyatnlkov wrote:

> [...] But on both systems it
> consumes too much of the CPU. I tried using live555 for the reception of
> 100 audio streams (g.711). It consumed about 10% CPU on my 3Ghz machine. I
> end up rewriting it with a simple set of asynchronous sockets, the CPU
> consumption fell to 1% at peak levels on both Linux and Windows.

Would you please share also some of your code?

If the performance improvements are so radical, why do not try to have those 
improvements merged back in live555 official releases?

-- 
ESC:wq

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel