Page History

...

The server requirements below are based on providing Yellowfin users with a responsive application user experience, however, any Yellowfin functions that query a data source, such as generating a report, loading filter values or caching results to a table, are susceptible to the performance of systems outside of the Yellowfin environment. Queries to slow external systems, can give the impression that Yellowfin itself is slow. It is recommended that external data sources be provisioned adequately for the number of data source requests that a number of concurrent Yellowfin users could generate simultaneously.

Functional Application Server Requirements

Yellowfin requires a minimum specification to be functional. The Yellowfin service will start on the following server specification:

...

Note: This specification is only recommended for a single concurrent user. Use of some functions (map generation, Assisted Insights), and reports on large volumes of data, may slow the machine and cause Yellowfin to use more memory than available. 32-bit machines are not recommended, as it enforces a hard limit on the amount of memory that can be allocated to Yellowfin.

Recommended Application Server Requirements

The recommended server configuration below would suit an environment up to roughly 25 concurrent users with average content complexity. 

...

Note: The specifications above are for a dedicated Yellowfin Server, with no other significant software running on the server other than the operating system. Running a database or other software on the same server would require additional RAM and CPU to meet the recommended minimum specification.

Recommended Repository Database Requirements

Yellowfin requires a database for storing metadata for the content and users that are in Yellowfin. It is recommended that this database reside on a separate server to where the Yellowfin application resides.

Reporting Database Requirements

In many cases a reporting database may exist prior to Yellowfin being provisioned. This may be a transactional database or data warehouse. In some environments, there may be multiple data sources that a single instance of Yellowfin will connect to. It is important that this database system can handle the queries that Yellowfin will generate. It is also important to understand that a single Yellowfin dashboard, with 5 reports, will generate 5 concurrent database queries on a reporting database. Ensuring these queries can be completed quickly will ensure that the dashboard loads in a reasonable time.

...

When reporting against a transactional system, it is important that columns are indexed to support reporting. Indexes for transactions are usually on ID columns, whereas report queries will filter by dimensional columns.

Client Requirements

The client machine is where a user will connect to Yellowfin from. Users will connect to Yellowfin through their web browser. Some Yellowfin reports can be large and it requires memory and processing power to render this in a browser.  Yellowfin also makes extensive use of JavaScript. This code is run in the browser and requires some processing power to execute.

It is difficult to recommend a specification for a client machine, as each user will have different programs (with different memory and CPU requirements) running on their desktop computer simultaneously. The following can be used as a guide, but it assumes that there are no other resource intensive processes running on the computer.

Server Requirements Concurrent Users

The following information is given based on benchmarks using Yellowfin in a basic scenario with moderate usage rates. Yellowfin recommends that you conduct your own benchmarking in an initial phase of your deployment to better understand hardware requirements based on your report content and user habits.

...