Il Wednesday 19 March 2008 23:44:10 Glen Gray ha scritto:
> Hey Marco,
> Did you make any progress diagnosing this problem ?
Not yet, my company seems to want to "fix" that issue buying a 9000$ licence
for a commercial RTSP server, and so postponed my work on optimization :-(
When I'll able to
Hey Marco,
Did you make any progress diagnosing this problem ?
--
Glen Gray
[EMAIL PROTECTED]
On 18 Mar 2008, at 09:09, Marco Amadori wrote:
> Il Monday 17 March 2008 23:11:52 Ross Finlayson ha scritto:
>>> So it seems to be a strange threading or concurrency problem
>>
>> Unlikely, because t
> > >So it seems to be a strange threading or concurrency problem
>>
>> Unlikely, because the LIVE555 code is single-threaded.
>
>Do you think it could be easely extended to be multithreaded?
No, because the system was explicitly designed to be single threaded,
using an event loop - rather than
Il Monday 17 March 2008 23:11:52 Ross Finlayson ha scritto:
> >So it seems to be a strange threading or concurrency problem
>
> Unlikely, because the LIVE555 code is single-threaded.
Do you think it could be easely extended to be multithreaded?
> You're clearly running into a resource limit; the
>So it seems to be a strange threading or concurrency problem
Unlikely, because the LIVE555 code is single-threaded.
You're clearly running into a resource limit; the question now is:
Which resource? Because your 95-stream limit seems to be happening
per process (rather than machine-wide), the
Hi all,
I tried live555MediaServer from 1.19.2008 tarball on a debian sid (both i386
and amd64) on 2 different IBM servers.
With both hardware and with kernels 2.6.22 and 2.6.24 I found that I cannot
cross the 95 contemporary MPEG2 streams limit (4.5 Mbps) without having
visual artifacts. *
On
