Forum Discussion
New Skype for Business on Mac Insider build available (16.13.168)
Hi Brian,
I'm not sure why it takes 14 seconds - it's not my area of expertise. That's part of why I posted above.
Until someone who knows SfB performance factors chimes in, here are some guessed-at possibilities:
- There are 7 people on the call, which could add to the desktop sharing setup time.
- The 7 people are in two continents, with a 170ms ping latency on the dedicated network link in between. If the desktop sharing setup protocol is chatty (i.e. a lot of network round trips), those round trips could add up to a significant delay.
- There's a mix of VbSS-capable and RDP-only capable clients on the call. There may be some time needed to negotiate what screen sharing protocol to use.
- Some other screen sharing platforms run a test on the network to determine available bandwidth, which adds to the setup time - don't know if SfB does this.
- There may be some time to negotiate frame rate. Don't know if SfB does this.
- If there's any transcoding of desktop sharing streams - I don't know if SfB does this - e.g. from VbSS to RDP - this could add to the setup time.
- My MacBook Pro 13" 2016 becomes very laggy when running SfB screen sharing. It could be that the RDP-based screen sharing on the SfB Mac client is inefficient, and contributes to the setup time.
Cheers,
-Tas.
Tas,
Are you using SfB online or on prem? What happens if you try to initiate a P2P screen share; does it take the same amount of time? SfB will default to RDP if any user does not have a VbSS client. This sounds to be like it could be more network related than SfB function.
We have over 500 Mac's in our environment. The SfB Mac client has come a long way in a little over a year from his GA release. I am running hybrid. In both scenario's online or on prem it doesn't take this long. In fact, every Wednesday we do a conference call with over 100 users on it and a screen share still doesn't take that long.
Brian - did you see this start up time in a meeting or in a one-on-one conversation? We have just discovered an issue that causes one-on-one conversations to always fallback to RDP and not use VbSS. We will be fixing this in a coming release. That could account for some of the start up delay.
If you can repro this again, please use Help/Report an Issue from an Insider build to send us the logs so we can investigate.
Phil.
I am not having a problem but the previous user is.
