Every time I’m in a meeting I experience approximately 2-5 seconds latency between clicking a button and getting the desired action (join, mute, move to a breakout room, leave, etc.). I always use the FCC desktop app. I don’t experience perceptible latency on Zoom, Teams, Meet, or Go to Meeting. My computer, broadband equipment, connections, and delivery are excellent in all other uses. Is this attributable to the capacity of your servers, or is there a setting somewhere that I could tweak?
Desktop App: v. 3.2.7316-6e02416
Test results: “Check Connection” 55ms latency, “OK” download, 9.8 mbps upload; Speedtest.net: Local - 7ms ping, 164mbps down, 10 up; Los Angeles - 53ms ping, 163mbps down, 10mbps up; Frankfurt - 141ms ping, 94mbps down, 10 mbps up.
Equipment: Intel Core i7 @ 1.90 GHz, Windows 10, 64 bit
Hello,
This is not because of the network. This is because of the overloaded GUI thread (CPU overload). We are doing some modifications to offload the GUI thread. It shall start feeling better in the with the next two releases.
Thank you,
Eugene
Thank you for your quick response. That makes sense. Talking with other hosts, I believe the action occurs almost instantly when I press a button and the delay I’m seeing is just slow response within the GUI. Looking forward to the updates!
Good morning. There have been several updates since we last spoke and the latency hasn’t improved. Has this been an issue for others too?
I use FCC happily every day for a particular meeting six days a week. Several of our regular attendees have also mentioned this latency and have started asking whether we should consider changing platforms because they say, “FCC just doesn’t feel as reliable” to them. I’ve tried to explain the GUI issue, but to average non-technical users, it’s all about the experience. They all have experiences with other platforms in other parts of their lives from which to draw comparisons. I prefer to stay with FCC and will continue to argue for that but I hope I don’t lose my meeting attendees over something that isn’t an actual reliability problem. Thanks for all you do.
Hello, we’ve added several improvements recently. Although it looks like it was not enough for your case. I’ve sent you a private message with the offer to troubleshoot the problem together.
Thank you,
Eugene