Hi Alexander,
On Thu, Jun 20, 2013 at 11:10 PM, Alexander Schremmer
a...@alexanderweb.de wrote:
The process itself only needs 40% CPU of 400% (dual core, dual
threaded).
There's one more thing to say: liquidsoap essentially only uses one
core at a time. There are two reasons for this: in the
On 19.06.2013 05:17, David Baelde wrote:
The catchup thing is when liquidsoap did not manage to compute its
stream fast enough for sending on time. In my experience this is
caused by lack of CPU, so I'd advise to look this way. It could be
that a latency on the filesystem or network is making
Hi,
2013/6/18 liquids...@aolohr.com:
Hi all,
Just a little addendum on 'catchups' that we were experiencing (and
finally solved):
Our IP uses FreeBSD servers, and our particular server has massive
resources,
lots of CPU power, 2.5 GB RAM, and abundant Bandwidth - 5 TB. So, tracking
down
Hi guys,
These issues are hard to fix, as they depend on a lot of factors. We
should keep watching out for what liquidsoap could do better, but so
far I don't see how the tool itself could help here.
Instead, I thought I would do a quick recap on what overruns/underruns
and we need to catchup
Hi all,
Just a little addendum on 'catchups' that we were experiencing (and
finally solved):
Our IP uses FreeBSD servers, and our particular server has massive
resources,
lots of CPU power, 2.5 GB RAM, and abundant Bandwidth - 5 TB. So, tracking
down these
devils was a real nightmare.
On 12.06.2013 10:20, Alexander Schremmer wrote:
Are the times when this problem happens consistent? Try setting the the
CPU priority of Liquidsoap to the max and see if that helps:
No, but the other processes might demand resources irregularly.
I will give it a boost to -5 (-19 sounds a
On Wed, Jun 12, 2013 at 10:20:51AM +0200, Alexander Schremmer wrote:
Now I have another issue left: after I set a metadata item via telnet, I
get spurious skips that look like this in the logs:
2013/06/12 10:16:24 [server:3] New client: localhost.
2013/06/12 10:16:24 [server:3] Client localhost
I wonder if your system experiences CPU usage spikes from cron jobs or
something similar that causes Liquidsoap to fall behind.
Are the times when this problem happens consistent? Try setting the the CPU
priority of Liquidsoap to the max and see if that helps:
to find pid: ps aux | grep liq:
to
