If Quickmap is going slowly, the biggest cause of this is a network timeout. Basically, Quickmap may be set up to point to a data location that doesn’t exist, and Quickmap goes slow while Quickmap is waiting for Windows to tell it that a file or folder is not accessible. To fix this either upgrade to Quickmap version 8 which doesn’t have this problem, or navigate to the following registry locations (start -> Run -> regedit.exe), and remove references to computers, data or network locations that no longer exist:
Another big cause of Quickmap going slowly is having the Quickmap data in a different geographic or network location than the Quickmap clients. For example, if your Quickmap data is stored in the Auckland office and you have Quickmap running from a remote laptop or another office, accessing the data over a VPN, Quickmap would run slowly and have issues accessing the network drive. As is best practice with any software, the software’s data should be stored in the same place as the software. For Quickmap this means either having standalone installations for remote users, or a local copy of the data (which can be maintained using the Quickmap Data Download Manager or by copying the data with scripts), or having a Terminal Server set up at the location of the data for remote users to access (which can even be a Published Application so it looks like Quickmap is running locally to the user).
If Quickmap or one of it’s components is still going slow after this, the next thing to determine is why it’s going slow, or rather what about it is going slow. To do this:
- Press CRTL + SHIFT + Esc, then click on the Performance tab.
- Run Quickmap and perform the function that makes it slow. Keep an eye on the CPU, Memory and Disk to see which is taking the biggest hit.
- If CPU goes close to 100% for more than a split second, the CPU usage needs addressed.
- If Memory is high (90%), then memory usage needs addressed.
- If the Disk gets higher than 10%, then there is likely a disk problem.
Once the resource is identified as slow (CPU, Memory or Disk), we need to repeat the test again and view the Processes tab, sorting by the appropriate resource type (CPU / Memory / Disk) to list the program with the highest to lowest usage.
If Quickmap is using most of the CPU or memory, then there may be an issue with your Quickmap installation, reinstalling may help.
If CPU or memory usage is high and shared with other programs, there is likely a performance issue with your PC (maybe your PC hardware isn’t fast enough, your antivirus scanning is excessive or another program is at fault). The most likely issue is the antivirus. QuickMap should not take longer than a few seconds to draw a screen of information, even on a slow network. If its taking longer than a few seconds, then contact you system administrator to take a look at the virus scanner on the PC that is running slow (rather than look at the server). Custom Software doesn’t provide support for configuring virus scanners, but recommends that you exclude the Quickmap directories (specifically it’s *.mdb, *.qik and *.exe files).
If your disk usage is high, then you most likely have an impending hardware fault with your disk. In this case, you should take the opportunity to backup your disk in case it fails and replace your hard drive with a new one.
If Quickmap is going slow and it’s not clear why with the above tests, you may have something else going on that it too complex to troubleshoot in this help article. An example of this might be if you have a network loop or internet connection that’s going slow, in which case you should contact your IT person for assistance. Also running Quickmap from a computer whose Quickmap data is accessed over a VPN or other slow network link, will make Quickmap run slowly.