similar to: icecast relay server performance testing

<div>Hi Alejandro,</div><div>Here is mine:</div><div><p><limits><br /> <workers>4</workers><br /> <clients>100000</clients><br /> <sources>2000</sources><br /> <queue-size>102400</queue-size><br /> <client-timeout>30</client-timeout><br />

I wrote a test application which is based on libuv. iptables is disabled. I’m running the test application from two other machines. Do you have any suggestions for testing? thanks! —zahar > On Jun 10, 2016, at 2:38 PM, Alejandro <cdgraff at gmail.com> wrote: > > Zahar, how are you testing? with some CURL stress test? BTW, IPTABLES is enabled? > > I was running most time

Sorry, 35K concurrent with 8 workers at 60% cpu 2016-06-10 1:28 GMT-03:00 Alejandro <cdgraff at gmail.com>: > Hi Zahar, what value has into > > <workers>8</workers> > > This value is recommended to set at 1 by virtual core. > > I 'm using for some years, KH branch with 35 concurrent listeners into 8 > core vm. > > Regards, > Alejandro

I’m going to try to run multiple curl processes. The libuv code that i wrote is not of a very good quality (even though it’s really simple). thanks! —zahar > On Jun 10, 2016, at 2:43 PM, Alejandro <cdgraff at gmail.com> wrote: > > In the past, i had used this method: > > http://icecast.org/loadtest/1/ <http://icecast.org/loadtest/1/> > > But to be honest,

Hi Alejandro, Many thanks for your message. I changed it to 4 (i have 4 cores), but it didn’t really help. I see that all 4 cores are now working, but the connections are still being dropped. Which VM type are you using? Or it’s not running on AWS? thanks! —zahar > On Jun 10, 2016, at 1:29 PM, Alejandro <cdgraff at gmail.com> wrote: > > Sorry, 35K concurrent with 8 workers at

Hi Philipp Thank you for chiming in. The only reason i use the -kh fork is because it seemed to be more recent. I had this performance issue with the regular version and tried the fork. I realize that the problem can be with the TCP stack parameters. I had no problem getting about 800Mbps between these machines when using iperf. Certainly, the workload completely different, but at least i know

In the past, i had used this method: http://icecast.org/loadtest/1/ But to be honest, nothing be compared with real use case, we found many issues when the connections arrive from many differents IPs, the stress test open all from small set of IPs, but almost this test case is used for many others, and present good results. 2016-06-10 2:40 GMT-03:00 Popov, Zahar <zahar.popov1978 at

Zahar, how are you testing? with some CURL stress test? BTW, IPTABLES is enabled? I was running most time in VMWARE, but i run 10k users in medium size box in AWS, just move out for the high transfer cost. 2016-06-10 2:36 GMT-03:00 Zahar Popov <zahar.popov1978 at yandex.com>: > Hi Alejandro, > Here is mine: > > <limits> > <workers>4</workers> >

Please share your config, almost the LIMITS part, this is my setup <limits> <workers>8</workers> <clients>100000</clients> <sources>700</sources> <queue-size>524288</queue-size> <client-timeout>30</client-timeout> <header-timeout>15</header-timeout>

Hi Zahar, what value has into <workers>8</workers> This value is recommended to set at 1 by virtual core. I 'm using for some years, KH branch with 35 concurrent listeners into 8 core vm. Regards, Alejandro 2016-06-10 0:50 GMT-03:00 Zahar Popov <zahar.popov1978 at yandex.com>: > Hello > I'm trying to measure the performance of the icecast relay server on

Good noon, On Fri, 2016-06-10 at 12:50 +0900, Zahar Popov wrote: > Hello > I'm trying to measure the performance of the icecast relay server on > 64kbps streams. > > The server is running in AWS [...]. I'm using the icecast-kh fork. > [...] > I'm able to go up to around 9K simultaneous connections to the server > (from two machines). [...] First: -kh is a

Am 05.08.2018 um 21:40 schrieb Paul Martin: > > Fallback to a file just fills up buffers as fast as it can. Not a > good idea at all as Icecast will keep buffering pretty much until it > runs out of memory if you're operating a relay. Better to use a local > encoder (eg. liquidsoap) which does proper rate limiting. Thank you, but the buffering is not my problem, because

Am 07.08.2018 um 14:52 schrieb Paul Martin: > Are you using the standard icecast2 or the kh (Karl Heyes) version? What is the difference between these version? I think kh is the developer and this version is newer (or better?) There can I get this kh-version?

Hello, I'm using Icecast over 10 years, so let me first say *Thank you to all developers* of Icecast! I have a problem using a mount with relay and a fallback. The option <fallback-override> is not working. I tested two different configurations: _Configuration A:_ ??? <mount> ??????? <mount-name>/Stream-096k.mp3</mount-name> ???????

Hi Hopefully this is the correct mailing list. Sorry if not. I am still fighting to install "shiny" on Solaris OS. For this I need the package 'httpuv' which makes troubles during linking. R version 3.0.1 (2013-05-16) -- "Good Sport" is working well. The compile steps result is below. I have more a general question. The problem is clear: The symbol

Hi all, Why is libuv-devel missing in CentOS-8? The rpm for libuv is preset but libuv-devel is not there. Adrian -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

EPEL package but I think there's a packaging bug, thought I would ask here. Trying to build something that requires libuv-devel - it finds the .so but can't determine version. header files are in /usr/include/uv however the pkgconfig file specifies /usr/include as the include directory. The pkgconfig file also has the version so I'm not sure why the make file can't determine

I'm running ices-kh to stream from jack at 64kbps, and also using oggenc (with ecasound via jack) to record the audio to disk at the same time. This is also running at 64kbps. ices is using virtually no cpu (0.0%), but oggenc is using 15-16%. I can't see why there should be such a difference - both are recording the same audio stream in real time at the same bitrate. oggenc is getting its

I'm running ices-kh to stream from jack at 64kbps, and also using oggenc (with ecasound via jack) to record the audio to disk at the same time. This is also running at 64kbps. ices is using virtually no cpu (0.0%), but oggenc is using 15-16%. I can't see why there should be such a difference - both are recording the same audio stream in real time at the same bitrate. oggenc is getting its

Hi, On 2 Sep 2024, at 12:19, Marek Dziembowski wrote: > Greetings icecasting amigos! > > > I?ve had an incredibly frustrating journey getting a new icecast origin server going to supplant an older machine set for retirement. > > The setup is relatively simple ? a beefy Debian bookworm host running icecast as a relaying slave pulling the streamlist from an icecast2 2.4.4 ingest