CPU spikes cause constant stuttering on on-demand servers due to steal time.

[Windows_2000]

The "real" solution would probably be to prioritze playback over other stuff, so it's everything else that gets slowed down, tho I understand that might be difficult to do.

Alternatively, it would be really nice to have an option, to, as an example, make Sinusbot artificially increase CPU usage for a short period before it needs it.

more detailed explanation:
I'm running Sinusbot (the only decent music bot for teamspeak, that doesn't have 1000 dependencies, that vary with each distro, thanks to the docker container) on an on-demand instance. I have never had this issue with anything (TeamSpeak server, a bunch of scripts, game servers etc. etc.), even with other ytdl music bots. But specifically Sinusbot spikes CPU usage (to about 20-30% from almost nothing), which causes a lot of stuttering, due to CPU not being available instantly from the hypervisor and it not prioritizing playback, over fetching other music (at least that's what I assume it is).

 

[Justman10000]

The "real" solution would probably be to prioritze playback over other stuff, so it's everything else that gets slowed down, tho I understand that might be difficult to do.

Alternatively, it would be really nice to have an option, to, as an example, make Sinusbot artificially increase CPU usage for a short period before it needs it.

more detailed explanation:
I'm running Sinusbot (the only decent music bot for teamspeak, that doesn't have 1000 dependencies, that vary with each distro, thanks to the docker container) on an on-demand instance. I have never had this issue with anything (TeamSpeak server, a bunch of scripts, game servers etc. etc.), even with other ytdl music bots. But specifically Sinusbot spikes CPU usage (to about 20-30% from almost nothing), which causes a lot of stuttering, due to CPU not being available instantly from the hypervisor and it not prioritizing playback, over fetching other music (at least that's what I assume it is).

The website says otherwise...

You don't need a new virtual machine or a huge Java installation. The bot is tiny and tries to do its best not to waste resources. A running bot will only take a few megabytes of RAM and little CPU usage.

 

[Windows_2000]

You don't need a new virtual machine or a huge Java installation. The bot is tiny and tries to do its best not to waste resources. A running bot will only take a few megabytes of RAM and little CPU usage.

IT does not matter how much it uses. What matters is that it spikes and while doing so doesn't prioritize playback over fetching songs. This means, that the on-demand VM gets a bunch of steal time and the bot stutters. It's not about it taking a lot of resources, it's about spiking and not prioritizing smooth playback over fetching of new songs.