Join us for live Q&A, tech support, and Speedify update news from our developers.
- This event has passed.
Speedify LIVE Office Hours: Q&A with the Developers
September 21 @ 2:00 pm - 3:00 pm
On the 131st episode of Speedify LIVE we hold our weekly Office Hours with Speedify Developer, Brian Prodoehl to discuss what’s new and what’s next for Speedify!
We take audience questions, chat about the latest improvements in Speedify 12.5, and how we make sure that our server locations are always available to users, even when there’s more traffic on them!
Here are our 5 takeaways from our Office Hours:
- Speedify 12.5 is now out on all platforms! We’ve made a lot of under-the-hood fixes, but also improved Connection Naming, we updated how Bluetooth connections are recognized, added a Reconnect feature on Windows, fixed Speedify sharing on the latest Raspberry Pi OS, and added a Bypass option for the Tesla app!
- The Speedify Reconnect feature is currently only available on Windows (for now). This feature gives you a pop-up after disconnecting where you can choose to Reconnect after 5 minutes, 2 hours or tomorrow, or Stay Disconnected. This will help make sure that you’re always covered by Speedify!
- By default, we set Bluetooth connections to Backup, and Speedify is now even better at recognizing these connections and setting them to the correct Priority. Bluetooth is a lot better designed for close-proximity devices like keyboards or headphones, but when sharing internet via Bluetooth it’s very limited in the speed it can provide, so we recommend that it’s used only as a last resort!
- When it comes to anticipating high server traffic, we do a lot of monitoring using Prometheus and Grafana, so we can make sure that we don’t cut it close! Whenever we feel like servers may be getting overloaded, we tend to scale up and order more servers to make sure that our users are always able to connect to our servers!
- Speedify on Android vs iOS can pretty much provide the same quality and performance, but there’s some key differences too! iOS has hard memory limits, where if Speedify touches 15Mb of memory, it will kill the app. Similarly, in case of a lot of traffic over a lot of time, we can run into CPU limits on iOS, while Android is a lot more likely to just let Speedify run in the background.
Our strategy is over-provisioning. We have too many servers, and no one has to wake up in the middle of the night if one server crashes.