MapLink Pro Studio System Requirements
MapLink Pro Studio System Requirements

In general, MapLink Pro Studio works best with lots of memory and lots of disk space. The more memory you have, the more you can assign to the vector and raster tiling caches and the faster it will be to create maps. Disk space requirements are mostly dependant upon your data – allow 5Gb for a typical MapLink installation not including data.

Although it will run on smaller machines, the minimum reasonable specification is:

  • Windows 7
  • 2 Gb of memory
  • 2 GHz processor.

The recommended minimum specification is:

  • Windows 7
  • 4 Gb of memory
  • 3 GHz processor

The following processors are supported:

  • Intel® Pentium® 4 processor family and higher.
  • Non Intel® processors compatible with the above processor supporting the SSE2 instruction set.

MapLink Pro Studio for x64

  • Early AMD x64 bit processors which lack support for CMPXCHG16B are not supported as this operation is required. These processors are the original "AMD Opteron Generation 1" (revision E and earlier).

A faster processor and more memory will allow large maps to be generated faster.

Primarily MapLink Pro Studio is single-threaded, MapLink Pro 7.0 introduced multi-threading for raster re-projection and pyramiding. Therefore a multi-core processor is ideal if you are processing a lot of raster images. See Multithreading Options

For processing large amounts of data the following minimum specification is recommended:

  • Windows 7 x64
  • 8 Gb of memory
  • Dual 3GHz Processor.
  • MapLink Pro Studio for x64

MapLink Pro Studio is available as a 32bit process which has been built with large address aware turned on or as a 64bit process.

For extremely large raster/GeoTIFF images MapLink Pro Studio provides an option that splits the image into smaller, more manageable sized images. See Raster File Loading

With extremely large rasters and some vector datasets you may still need to ask your data supplier to split the data into smaller chunks.

Please also see Tips for Reducing Processing Memory Requirements