Last Updated: March 18, 2025
Using Maptitude on a server can sometimes result in slower performance compared to running it on a local Windows machine. This is due to multiple factors, including network speed, hardware limitations, and server settings. Below, we explore key factors affecting Maptitude’s speed on a server and ways to optimize performance.
Table of Contents
- Ensure You Are Using the Latest Version of Maptitude
- Fair Sharing and Network Speed
- Hardware Considerations
- Understanding Server-Based Map Rendering
- Benchmarking Maptitude Performance
Ensure You Are Using the Latest Version of Maptitude
Keeping Maptitude updated ensures you benefit from the latest fixes and improvements. If you are experiencing performance issues, make sure you are running the latest version.
Fair Sharing and Network Speed
Map drawing speed can be impacted by Fair Sharing settings in Windows Server. These settings distribute resources among users but may slow down Maptitude. You can check or disable Fair Sharing to potentially improve performance:
Additionally, Maptitude’s speed when accessed remotely (via Remote Desktop, Citrix, Terminal Services, or Amazon EC2) largely depends on network speed. Work with your IT team to analyze network traffic and optimize speed where possible.
Hardware Considerations
Video RAM and Graphics Rendering
A major difference between a local Windows machine and a server is the availability of dedicated video RAM. Many servers lack a dedicated video adapter, which can significantly impact Maptitude’s performance. Performance typically scales with available video memory, so consider a server with dedicated GPU resources for better results.
For more details, refer to:
Security Software Impact
We have observed improvements in operations such as geocoding when disabling anti-malware and antivirus applications. Running multiple security programs simultaneously can slow down Maptitude. While security software is essential, optimizing it for minimal interference can help boost performance.
Understanding Server-Based Map Rendering
When using Maptitude on a server, map drawing occurs on the server, and the map images are repeatedly generated and sent over the network. This process inherently introduces latency, especially when multiple users are accessing Maptitude simultaneously and competing for the server’s finite resources.
Benchmarking Maptitude Performance
To measure Maptitude’s performance differences between a local Windows machine and a server, try the following benchmarks:
- Basic Query Benchmark
- Open your data source in Maptitude via File > Open.
- Use Select by Condition to run a simple query.
- Compare execution times between the local and server versions.
- Map Performance Benchmark
- Create a sample map without external data sources and test its speed on both systems.
- Geocoding Benchmark
- Geocode the “Sample Customers for United States” Excel file, found in the tutorial folder, and compare results.
These benchmarks can help pinpoint areas where performance differences are most noticeable.
Maptitude’s performance on a server is influenced by several factors, including network speed, hardware specifications, Fair Sharing settings, and security software configurations. By optimizing these areas and running performance benchmarks, you can improve Maptitude’s efficiency in a server environment.
For more information on basic system requirements to run Maptitude, please refer to this article.