Displayr is a highly resource-intensive application. If your computer has insufficient resources, this will cause Displayr to slow down. Generally, the more data and the more calculations you have, the more severe any of the issues described below will become. Things to check are:
- Internet connectivity
- The computer's resources
- Number of programs open
- Chrome extensions
- Other browser performance problems
If you are regularly getting strange errors when using Displayr, the most common cause is a poor internet connection. As Displayr works by sending information from your computer to a server, and then returning results from the server to your computer, the program is severely impacted by poor internet connections.
You can diagnose speed issues using:
For the Displayr test, you should expect to get something less than about 350 ms for the ping, and a good transfer speed is somewhere above 1MB/s or more.
For the Speedtest.net version, you should get at least 5Mbps for your download and 1Mbps for a small upload. The graphs should also look flat/stable rather than having a lot of peaks and troughs.
The computer's resources
Displayr does not require a special computer to run. However, if your computer is old and slow at most things, then this will mean you find using Displayr slower than you otherwise would.
Check that you are using the latest version of your browser and that you are using a widely available modern browser (e.g., Chrome). If using a Mac, Chrome is advisable.
Number of programs open
The more programs that are open on your computer, the fewer resources that will be available for your browser, which will in turn make Displayr slower.
Number of browser tabs open
Chrome shares resources across all the tabs that are open. The more tabs you have open, the greater the likelihood that this will impact Displayr's performance.
Chrome extensions consume resources on a PC. By starting Chrome in private mode (extensions don't run in private mode) you can see if this is the cause of problems.
Other browser performance problems
Run browser benchmarks from within Chrome in normal mode to get a better understanding of your computer. The benchmarks take a total of 10-15 minutes:
Keep in mind that there is latency (though on the scale of milliseconds) with using cloud-based products that have to communicate with servers that may be thousands of miles away vs software that is on your local computer. When you click on multiple things before they finish processing or have multiple users editing a document at the same time, this causes more communication with the cloud servers, such that the document is kept in sync. This adds to the latency. There could also be processes running in the background in Displayr that may appear like a latency issue, but is merely Displayr being busy, see Understand Why a Document is Busy.