Zoomdata Version

Sizing Guidelines for the Zoomdata Server


The Zoomdata Server is designed to query large scale datasets and newer generation databases quickly and efficiently.  Visualization results are produced within seconds of the original query and sharpened over time. In order to maximize the operational efficiency of Zoomdata, it is necessary to take into account the following factors to appropriately size the Zoomdata Server in your operating environment:

  • Number of concurrent users during peak access times
  • Size of the data sources that will be connected to the Zoomdata Server

This article provides sizing guidelines to optimize the Server for responsive, multi-user queries. Table 1 provides a high level description of the Sizing Profiles recommended for the Zoomdata Server.

Table 1: Description of the Zoomdata Sizing Profiles

Sizing Profile

Profile Description

Demo, POC The most basic profile, supporting 1-2 concurrent users.
10s of Users

For the smaller organization that will have less than 100 users at any given time.

100s to 1000s of Users

For the mid-size to large organizations that will have 100 or more users at any given time.

Contact Zoomdata Technical Support to get help in setting up Zoomdata in your operating environment in the best configuration possible.


Zoomdata is designed to be performant on different Linux environments including RPM for RedHat, CentOS and Scientific Linux as well as Ubuntu. In addition, Zoomdata uses websocket technology that is supported only by modern day web browsers. Table 2 identifies the OS and browser requirements that have been tested and verified to support Zoomdata.

Table 2: Server Operating System and Client Browser Requirements

Sizing Profile OS Platform Access Requirements: Browsers
Demo, POCs

Linux 64-bit

  • CentOS, RHEL
  • Ubuntu
  • Windows 7+
    • Chrome 29 (recommended)
    • Firefox 23 +
    • Internet Explorer 10+
  • Mac OSX+
    • Chrome 29+ (recommended)
    • Firefox 23+
    • Safari 6.1
  • iOS 6+
    • Embedded Safari Browser
10s of Users

Linux 64-bit

  • CentOS, RHEL
  • Ubuntu
100s to 1000s of Users

Linux 64-bit

  • CentOS, RHEL
  • Ubuntu


Sizing the server containing Zoomdata requires using a performance profile based on the expected number of concurrent users that will be accessing Zoomdata during peak times. In addition, the size of the data source(s) being accessed by Zoomdata impacts the sizing profile. Scale-out and load balancing may also be needed, depending on the organization’s operating environment. (Refer to the article Configuring Zoomdata Server Behind a Load Balancer (article in development) for support on distributed environments).

Hardware requirements must be adjusted to account for both an increasing number of users and size of the data source:

  • CPU: number of cores
  • Memory allocated to Zoomdata
  • Disk space that may be used by Zoomdata

Table 3 details the sizing profile supported by the Zoomdata Server. Keep in mind that the specifications provided in Table 3 are suggested starting points and are minimum estimates only. Sizing Zoomdata for performance is impacted by, not only the factors mentioned, but also the operating environment where Zoomdata resides, the different number and types of databases used in the organization (for example, whether data is distributed between Oracle, Hadoop, and Search-based environments), the interactions between the apps and databases, and other factors.

The sizing profiles presented in Table 3 is based on an estimate of user concurrency, or the maximum number of users expected to be logged into Zoomdata at the same time.

What is the Difference Between Concurrent Users Versus Total Users?
Concurrent users represent only a portion of the total number of available users in an organization who may access the Zoomdata server at the same time. In general, Zoomdata approximates 20% of the total userbase to be logged onto Zoomdata at any given time. So if an organization has 1000 total users that have access rights to Zoomdata, we estimate that 200 users may be logged concurrently.

A single Zoomdata server has been tested for up to 100 concurrent users at any given time. When testing user concurrency, factors including the cardinality of the data sources, loading, sharpening, and visualizing results in dashboards were considered.

Table 3: Zoomdata Server Suggested Sizing Profiles
Sizing Profile (For Concurrency) Size of the Data Source CPU: # of Cores (Minimum) Memory allocation JVM Memory allocation Disk space (Minimum) Supported # of concurrent users (Per server) Assumptions

Demo, POCs, 1-2 users

Megabytes (MBs) of data


16 GB

8 GB


250 GB


Metadata store is embedded (on the same server as Zoomdata)

10s of concurrent users

Gigabytes (GBs) of data


64 GB


500 GB

<100 Metadata store is embedded (on the same server as Zoomdata)

100s to 1000s of concurrent users

Terabytes (TBs) to Petabytes (PBs) of data

Contact Zoomdata Technical Support 100+ Contact Zoomdata Technical Support
By default, the JVM memory setting is set to use a max of 8 GB. For 10s of concurrent users, the recommended allocation is 20 GB. For instructions to increase the JVM memory, refer to the article Configuring Zoomdata’s Memory Settings .

Select the green Support button for assistance with sizing your environment for 100s or 1000s of concurrent users.