• If you need help or want to discuss things, you now can also join us on our Discord Server!
  • A first preview of the unlimited version of SinusBot can be found in the Upcoming Changes thread. A version for Windows will follow, but we don't have a release date, yet.

Help with the operation Sinusbot & Youtube-Dl

n0ns.

Member
I would like to know if there are any possible settings in youtube-dl or in the sinusbot itself, so that it does not multiply the "youtube-dl" process when playing songs singly by more than 1 instance.
Example:
I have 4 bots of music on the server, if I request to play the song through the youtubeSearch plugin for the 4 bots at the same time, it creates 4 youtube-dl processes while forcing the cpu of my vps to the maximum and leading to crash `s.
And furthermore after the server crashes it seems that the processes start to multiply infinitely.
I would like to know some configuration that would not let that happen, that would only use one youtube-dl process and would queue the other requests to be processed at the end of the first conversion. That way there would be no multi-youtube-dl processes and nor would it take to the extreme the use of vcpu.

According to the attached print when executing the command "htop"
 

Attachments

  • Screenshot_3.png
    Screenshot_3.png
    195.6 KB · Views: 18

Xuxe

Containerholic
Staff member
is awesome!
V.I.P.
Contributor
Insider
Hi,

First: a high loaded server should not crash, never. - This a problem on your end or from your hoster.
AFAIK it's not possible limit youtube-dl one thread and if you shouldn't it will have impact on your sound quality.

So it's basicly your server which is to low to handle this load.

What do you get as output from:

Code:
cat /proc/cpuinfo
 

n0ns.

Member
[CITAR]
root @ kvmlinux: ~ # cat / proc / cpuinfo
processador: 0
vendor_id: GenuineIntel
cpu family: 6
modelo: 13
nome do modelo: versão da CPU Virtual QEMU (cpu64-rhel6)
revisão: 3
microcódigo: 0x1
CPU MHz: 2393,98
tamanho do cache: 4096 KB
ID Físico: 0
irmãos: 1
id do core: 0
núcleos de cpu: 1
apicid: 0
apicid inicial: 0
fpu: sim
fpu_exception: sim
nível de cpuid: 4
wp: sim
flags: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm nni pni cx16 hipervisor lahf_lm kaiser
insetos:
bogomips: 4787.99
tamanho clflush: 64
cache_alignment: 64
Tamanhos de físico: físico de 40 bits, virtual de 48 bits
gerenciamento de energia:

processador: 1
vendor_id: GenuineIntel
cpu family: 6
modelo: 13
nome do modelo: versão da CPU Virtual QEMU (cpu64-rhel6)
revisão: 3
microcódigo: 0x1
CPU MHz: 2393,98
tamanho do cache: 4096 KB
identificação física: 1
irmãos: 1
id do core: 0
núcleos de cpu: 1
apicid: 1
apicídio inicial: 1
fpu: sim
fpu_exception: sim
nível de cpuid: 4
wp: sim
flags: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm nni pni cx16 hipervisor lahf_lm kaiser
insetos:
bogomips: 4787.99
tamanho clflush: 64
cache_alignment: 64
Tamanhos de físico: físico de 40 bits, virtual de 48 bits
gerenciamento de energia:
[/ QUOTE]
 

Xuxe

Containerholic
Staff member
is awesome!
V.I.P.
Contributor
Insider
Thanks @Vini .
Looks good so far, so it's may a overloaded host.

Could you make a screen of 'top' for me? Or may copy/screen the output from "vmstat":

Code:
apt-get update && apt-get install sysstat #may needed after this do:
vmstat -w
 
Top