Page Comparison

Data Gateway Data Movement server

<tenant-id>.<region>.qlikcloud.com.

TCP 443 (HTTPS)

Data Gateway Data Movement server

Database servers gateway is connecting to

Listening ports on the DB server

IT Administrators workspaces

Data Gateway Data Movement server

TCP 22 (SSH)

Processor

Quad core

Quad core base

Dual-core per task

8-core base

Quad core per task

Additional cores are useful in any of the following situations:

• Many tasks running in parallel

• Full-load performance priority

• Multiple full-load processes running in parallel

Memory

8 GB

32 GB

64 GB

More memory is useful in any of the following situations:

• Many tasks running in parallel

• Long-running transactions on the source endpoint (for example, monthly batch processing)

• Many active users on the source system

Disk requirements
(SSD is recommended for optimal performance)

320 GB

500 GB

RAID

500 GB

RAID

A faster disk is useful in any of the following situations:

• Long-running source transactions that may not fit into memory

• Using tasks that are set up to continue processing during target outage

A larger disk is required in any of the following situations:

• Using tasks that are set up to continue processing during target outage

• Very large source transactions that do not fit into memory

RAID is recommended for system recovery in case of disk failure for all configurations.

Network

1 Gbps

10 Gbps

Two 10 Gbps

-

AWS Instance Recommendation

• t3a.large (2vCPU - 8GB RAM) - bare minimum

• t3a.xlarge (4vCPU - 16GB RAM) - recommended minimum

• t3a.2xlarge (8vCPU - 32GB RAM) - for spikes in day

• m7a.2xlarge (8vCPU - 32GB RAM) - for consistent loads throughout the day

m7a.4xlarge (16vCPU -

64GB RAM) - cost optimal

or c7a.8xlarge (32vCPU - 64GB RAM) - very intense CPU needs

AWS instance types can be modified after creation. Recommendation is to start small and increase if needed.