This message was deleted.
# helpdesk
s
This message was deleted.
h
For information, I'm running my own livekit server for test purposes, and I use the docker compose based deployment of the official documentation.
m
cc @chilly-animal-65189
c
We are using the gstreamer libvpx binding for encoding. I couldn't find any confirmation of whether vp8enc supports multithreading, but it does look like it may not, considering that there is an option in libvpx enable multithreading for vp9, but not vp8
What resolution are you encoding, on what kind of core? There are tweaks to adjust the cpu usage/quality tradeoff for vp8 encoding, They are set to the default values currently
And it's exposed at the gstreamer level, so we can set this to a different value
Still curious about your use case to understand a bit better what to set this to. It looks like there are some restrictions linked to frame size
h
For the moment, I test from 1080p to 480p, with quality from 0 to 2, and bitrate from 10kB/s to 500kB/s, nothing change, still 100% of one core and latency which increase
For the moment, we need vp8 because the python client sdk (based on the rust one) only support vp8.
c
What is the cpu core this runs on?
if we can't keep up on 1 core at 480p, multithreading is unlikely to be enough for 1080p
h
AMD EPYC™ 7281
I will try tomorrow on your cloud ingress to see if it’s my livekit setup or the server which cause the behavior
c
I have no doubt cloud will also fail at 1080p without multihreading. 480p is more interesting
d
@happy-ability-28669 We have not optimized Ingress for VP8 encoding yet. This is on our roadmap. Once completed it should have no issues utilizing multiple cores.
h
ok
Thank. Look forward to hearing from you
Any idea when the rust client will support the h264 ?
d
I believe 0.2.0 does!
h
Perfect. Thank you guys !
❤️ 1