Skip to main content

ArcGIS Velocity system requirements

Operating system requirements

Velocity has the same operating system requirements as ArcGIS Enterprise.

Hardware requirements

The ingestion and analysis of real-time data can be resource-intensive. The allocation and consumption of resources can be highly variable depending on the configuration.

For more information, refer to resource allocation considerations.

Review the following recommendations for deploying Velocity.

  • Production systems should have at least 16 GB of RAM. Newer RAM generations, such as DDR5, can improve real-time data throughput and processing. Use cases that may require additional RAM include the following:

    • Using a large volume of features as geofences.

    • Using highly complex features as geofences (polygons with thousands of vertices).

    • Monitoring the state of continuously tracked features, such as a fleet of uniquely identifiable vehicles.

    • Storing a large cache of static features for performing spatial, temporal, or attribute joins.

  • Deploy Velocity on machines with at least four physical cores and eight logical or virtual processors. Production systems should have at least eight physical cores to achieve adequate performance.

  • Use a high-bandwidth network connection, such as 1 GB or 10 GB, and storage that supports high input/output operations per second (IOPS) to reduce latency when receiving and sending real-time data.

Many production systems may require additional CPU cores and RAM depending on the volume of real-time data input/output and complexity of real-time analytics.

Velocity requires a minimum of 20 GB of disk space for installation.

Each configured item in Velocity requires additional disk space due to the underlying Kafka topic that Velocity Gateway creates. The topics queue and manage real-time data in transit from component to component within Velocity. These topics can grow to hundreds of MB per topic, sometimes exceeding 1 GB or more. A recommended starting point for production systems is 100 GB of disk space for Velocity. You may need additional disk space based on the number of configured items and the volume of real-time data your site handles.

Velocity also uses disk space to store configuration backups, logs, and more. During Velocity installation, the system administrator can choose the default deployment location. You can place configuration backups and logs elsewhere to help manage disk space.

Software requirements

Velocity requires federation with an ArcGIS Enterprise portal. You must have a base Enterprise deployment before you install Velocity on a separate machine.

Supported web browsers

Velocity supports the same web browsers as Enterprise.

Cloud implementation

Velocity supports cloud deployments on Amazon Web Services (AWS) and Microsoft Azure.

Hostname requirements

The Velocity machine must be able to resolve the hostname configured during site creation, not just external clients. If the hostname is a custom or internal domain not registered in public DNS, you must manually add an entry to the Velocity machine's hosts file.

Edit /etc/hosts and add the following entry:

Edit C:\Windows\System32\drivers\etc\hosts and add the following entry:

127.0.0.1 <your_velocity_FQDN> <your_velocity_short_hostname>

For example, 127.0.0.1 velocityexample.domain.com velocityexample

SELinux support

Velocity supports the Security-Enhanced Linux (SELinux) module. The default SELinux policy may prevent Velocity from accessing internal components such as the configuration store, so administrators may need to modify the SELinux policy. To do so, temporarily set the SELinux policy mode to permissive. This mode records policy violations, such as actions taken by Velocity to access internal directories, while allowing those actions to occur. Administrators can note these violations and modify the SELinux policy configuration to allow them before resetting the policy mode to enforced.