If you want to confirm whether network bandwidth is an issue, you can temporarily reduce the computer's resolution to 1024x768 or turn on smooth mode (in the Splashtop Business app), to see whether speed improves. Insufficient network bandwidth may result in delays of up to several seconds, but usually no more. Network bandwidth is not likely the reason when the delay is so drastic.
This support article shows where to look in DxDiag for the relevant info. You can run Windows's built-in DxDiag.exe to find out how much video memory the computer has. However, this approach does mean we tax the graphics hardware more heavily. That technology is key to achieving our performance goal of enabling users to feel as if they're still sitting in front of their computers (given sufficient hardware and network capabilities, of course). The reason why Splashtop needs more video memory than traditional remote desktop tools is we use a video-based approach to encode and transmit the screen. But it may not be met by many servers out there where 8MB or 16MB of video memory is still the norm. This is easily met by most PCs and off-the-shelf graphics cards nowadays (where 1GB+ is not uncommon). For Splashtop to work efficiently, the computer should have at least 256MB of video memory. If this is happening, it is an indication of Splashtop not having enough video memory to work with. It is still necessary to apply one of the two workarounds below so your server can operate the most efficiently.
Version 3.0.6.2 introduced an optimization that reduces the delay on servers with low video memory from potentially minutes down to a few seconds, so such a system can at least be operable. CPU utilization is also unusually high at 25-50%, even on a fast, multi-core CPU.
#SPLASHTOP PERSONAL NO MONITOR WINDOWS#
(Note that this issue does not happen on Windows Server 2012.)įor Windows streamer version 3.0.6.2 or later:ĭuring a remote session, screen updates are delayed by a few seconds and cursor keeps flashing.
0 kommentar(er)
