GpsGate requirements

This article describes server hardware and software requirements for GpsGate On-Site installations.

Read how to install GpsGate.

Requirements

Operative System

  • Microsoft Windows Server with x64 architecture (supported versions of Windows only). Windows 10/11 is supported, but not recommended for production environments.
  • static IP address assigned to your computer/server.
  • Chrome, Firefox, Safari or Edge as your default browser. Deprecated browsers are not supported.
  • .NET Framework 4.8 Runtime. Learn more here.

Database

  • My-SQL 8 or later (the latest version comes with the installer) or Microsoft SQL Server (2016 or superior).
  • Large installations (more than 5000 units): we recommend to use AWS Aurora as a database system. It has plenty of features such as real-time backup and easy to scale up when your installation grows.
  • IIS Express not supported.
  • Any non-supported/dated/deprecated DB system is not supported.
  • Installation on cluster environments: parts of the product can run in a cluster. This kind of setup can currently be done by request by contacting GpsGate support.

Connectivity

  • Make sure your router, proxy or firewall, is not blocking outgoing traffic for  *.gpsgate.com and *.gpsgateservices.com.
  • Open ports in your firewall for your GPS device's inbound traffic (ports are device dependant, each device brand use a different port). Read device troubleshooting for more information.

Hardware requirements

Hard disk

  • A full GpsGate installation uses around 1.5 GB of disk usage (database installation and usage not included). We recommend having at least 5 GB of free disk space in your computer/server for a successful installation.
  • In production environments, it is always recommended using reliable disks and data protection systems such as RAID1 or similar.
  • SSD disks types are recommended to improve performance.
  • A typical installation uses around 200 Mb per device and year. Device data usage is subject to different factors such as the protocol used to transmit information, the device brand/model and the frequency that the device uses to report to the server (the control over the amount of data stored in the server can be configured using the Cleanup feature).

CPU and memory

  • CPU and memory usage will depend on many factors, such as event rules introduced, devices reporting to the server and their frequency, the number of connected users making requests simultaneously, etc.
  • GpsGate server consumes about 150 MB of memory per 100 devices simultaneously online.
  • We recommend having at least 4 GB of RAM, but more is always better.
  • GpsGate Server makes good use of multi-core CPUs. Dual-core or higher is recommended.

Estimations on server resources

Transactions

  • 30 vehicles with an update once every one minute will give you an average of 0.5 transactions per second.
  • Depending on how many event rules you apply to each application, how many reports users execute at specific moments, each transaction will take a different amount of computing resources.

Bandwidth

Question: How many Mb of my SIM card data plan will be consumed?

  • GpsGate Server uses very little bandwidth. A transaction is often of less than 0.2 Kb.
  • A user logged into the web interface average about 2 Kb/sec.

Configuration references

Small system / personal use

  • 20 vehicles, update rate 1 minute.

You can use any Windows computer that meets the requirements listed above.

Medium system / small-medium company or organization

  • 500 vehicles, update rate 1 minute
  • Windows Server
  • MySQL 8 or later
  • 300 GB RAID1 disks
  • Dual-Core CPU
  • 4 GB ram or more

Large systems / big organizations

  • 5000 vehicles, update rate 1 minute on average
  • Windows 2012 R2 or later
  • MySQL 8 or later
  • 600 GB RAID1
  • 2 CPUs Quad Core (total number of cores: 8)
  • 16 GB RAM or more