HPCC is designed to run on thousands of nodes. At minimum, you need one current and supported Linux system to run a single node cluster. If you are interested in running HPCC on Windows please contact us. In addition, the ECL IDE is available for Windows and ECL Eclipse Plugin is available for all platforms. Detailed information is available in the system requirements guide.

No. It integrates Commodity-Off-the-Shelf (COTS) hardware.
Minimum memory per node: 4GB

Currently no single file can be greater than 4 exabytes (or 4 million terabytes). This is not a current concern as other limitations occur in real-world systems before this limitation is reached; such as total available disk space on your cluster. There are no theoretical limits to the number of files.

The data files and index files referenced by the query’s ECL code are made available in one of these ways, depending on the configuration of the Roxie cluster.

Two configuration settings in Configuration Manager determine how this works:

copyResources
Copies necessary data and key files from the current location when the query is published.

useRemoteResources
Loads necessary data and key files from the current location when the query is published.

These options may appear to be mutually exclusive, but the chart below shows what each possible combination means.

--------------------------------------------------------------------
copyResources T
useRemoteResources T

Directs the Roxie cluster to use the remote copy of the data until it can copy the data locally. This allows a query to be available immediately using the remote data until the copy completes.

--------------------------------------------------------------------
copyResources T
useRemoteResources F

Directs the Roxie cluster to copy the data locally. The query cannot be executed until the data copy completes. This ensures optimum performance but may delay the query's availability until the file copy completes.

--------------------------------------------------------------------
copyResources F
useRemoteResources T

Directs the Roxie cluster to load the data from a remote location and never copy locally. The query can be executed immediately, but performance is limited by network bandwidth.
This allows queries to run without using any Roxie node disk space, but reduces its throughput capabilities. This is the default for a single node because Thor and Roxie are on the same node and share the same disk drives.

--------------------------------------------------------------------
copyResources F
useRemoteResources F

Will use data and indexes previously loaded but will not copy or read remote data.

Logging in (e.g., being a registered user) allows you to post to the forums, contribute code and submit issues. Otherwise, anonymous users can only read these areas and cannot post or contribute.

No, you are free to keep your ECL source code for yourself. Only changes or improvements to the HPCC platform must be disclosed. There are no obligations attached to ECL programs.

A step-by-step guide with links to system requirements, documentation and other reference materials is available to help you get started.

To learn ECL, visit the Documentation area in the Community section of this website and read the ECL Programmers Guide and/or the ECL Reference Guide.

In addition to documentation, professional training and other tutorials are available. Visit the training section for more information.