Recommended Hardware Configuration

Scalability Guidelines Based On Customer Data

Based on testing and production results from several customers, Table 1 offers guidelines for expected user and/or data densities. Results vary based on many variables and doing your own testing will determine your specific scalability.

Table 1: Hardware/VM Usage Guidelines

¹ Complexity in this context is volume and frequency of change via Change Data Capture (CDC).

² Precise user counts will vary subject to the complexity of application usage, workspaces, reports, etc.

Tip: We recommend early discussions with the Hubble Support on appropriate hardware configuration for significantly higher user counts (and/or multiple data sources).

Analysis Summary

The combination of Data Volume and Data Complexity require significant CPU resources, so investing in higher CPU speeds and more cores will pay off in both performance and scalability. In Table 1 above, the combination of #1 and #5 may require use of the Advanced specifications as shown in the last column.

Hubble Accelerator Host Server Hardware

Table 2: Accelerator Hardware Host Server Guidelines

¹ Use of dual 4th Generation Intel® Xeon® Scalable Processors may be appropriate in some cases (beyond 250 concurrent users with multiple complex data sources, for example). Please discuss exact requirements with Hubble Support at early stages of your planning

² 1 GB/sec equates to read IOPS of 266,000 or greater.

³The primary storage for the Vector database is disk storage. Your storage solution must satisfy performance and space requirements. To achieve good consistent performance, you should choose smaller rather than bigger disks.

⁴Vector is optimized to work with both memory and disk-resident datasets, allowing it to efficiently process large amounts of data (hundreds of gigabytes). Vector can process data at more than 1.5 GB/sec per CPU core. To achieve this rate, the CPU cores must be fed at a rate fast enough to keep them busy. Consider making SSD technology a viable storage consideration for your system. It is recommended to choose SSDs for temporary database storage to improve performance for spill-to-disk operations i.e. Vector work area (II_WORK).

Hubble Accelerator Virtual Machine

Note: For optimal performance, it is recommended to run the Hubble Accelerator in a Virtual Machine on dedicated hardware. It should not be hosted on the same physical device as other Virtual Machines or business applications that could impact system resources.

Table 3: Hubble Accelerator VM Guidelines

¹This is the amount of RAM available to the applications and is based on a single replication data source. Additional RAM may be required for particularly complex or big data environments. RAM size may have to be increased post-implementation.

² Storage requirements will vary considerably by customer, depending upon the quantity of source ERP data and how much needs to be replicated to the Accelerator to service your reporting and analytics needs. For guidance, the typical compression ratio between source data in the ERP database and the accelerator is 4:3.

Architecture

Below is a diagram with the standard System Architecture of a Hubble Enterprise Deployment.

Components

Hubble accelerator installs:

• Actian Vector
• Qlik Replicate
• Hubble Backup API

Network Access

Below are defined all the ports a firewall needs to be configured with to ensure normal function of Hubble Accelerator as part of a Hubble deployment.