This message was deleted.
# cloud
s
This message was deleted.
a
if it’s 1080p 60fps you might be CPU bound
cc @chilly-animal-65189
i
do you mean the OBS client or do you mean the livekit cloud instance?
a
My bad, I didn’t realize this was in the cloud channel - I mean the cloud ingress instance, if it’s transcoding
i
got it, no worries. Yeah I have not put any transcoding in place
a
As for bitrate, I would expect 6 Mbps to be enough, but you could try going up to 12 or 15 and see if that gives better quality
i
got it, I used https://livekit.io/webrtc/bitrate-guide which suggested 8.5 MBps (gaming use case)
👍 1
@able-gigabyte-21598 is there a way to see percent of dropped frames as well as delay through livekit API (or dashboard)?
I like the idea of not having to self-host but it feels a bit harder to debug in practice when I have an issue. I just don’t know where to look
(I will try other bit rates to see)
a
you can go to the
Sessions
tab in the dashboard, and click on the room, then the ingress participant
❤️ 1
it’ll have charts for quality, framerate, bitrate, packet loss, etc
❤️ 1
i
awesome, sorry I missed that!
it shows that I am connected to a server in Germany region (I am currently in US East, not using any VPN)
Is there a way to provide some data locality hint? (request a US East server for instance)
(so there are 2 participants: streamer and client, both in US East. Streamer is correctly mapped to US East while client is mapped to Germany)
a
I’m not sure what the state of ingress routing is, benjamin will be able to answer that one. It should do it automatically based on IP, but that might not be implemented yet
👍 1
i
Got it, okay! Good to know 🙂
That would be a great feature
c
We have 2 ingress regions, US east and EU, and DNS based latency routing on top of it. Where was the whip encoder located?
i
Livekit server region: US East for whip streamer and germany for watcher
Actual: US east for streamer and germany
c
Not sure about the Germany part, but the link between our datacenters should not be the problem here
i
(sorry I meant actual: US east for streamer and viewer 😅)
yeah this more minor I suppose but it does add latency (100-150ms between US East and germany) so any ability to let clients pick in the API would be welcome
d
it's interesting it routed you to Germany, we'll take a look at that.. typically it would route you to the closest region by DNS.
❤️ 1
i
thanks @dry-elephant-14928 - it’s definitely not a blocker right now but just thought that I would mentioned it
👍 1