Page History
...
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yellowfin Data Discovery and Yellowfin Dashboards, both require the following minimum specification to be functional. Functional Application Server RequirementsThe Yellowfin service will start on the following server specification:
Note: This specification is only recommended for a single concurrent user. Use of some functions (such as, 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 RequirementsThe recommended server configuration below would suit an environment of 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 RequirementsYellowfin 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.
Source Database RequirementsIn many cases a source 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 source database. Ensuring these queries can be completed quickly will ensure that the dashboard loads in a reasonable time. The requirements are different based on the type of database system in use, and the amount of data in the system. For example, a MySQL instance with 10,000 rows of data, will provide much faster query times than a MySQL instance with 10,000,000 rows of data on the same hardware. High-speed columnar databases such as HP Vertica, Sybase IQ and Actian Vector will provide much faster query times on the same hardware as a relational database with the same amount of data. When querying 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 RequirementsThe 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 them 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 computers simultaneously. The following can be used as a guide, but it’s assumed that there are no other resource intensive processes running on the computer. However, Microsoft is phasing out support for its browser, Internet Explorer 11. As a result, Yellowfin software is no longer supported to run on IE11 and we can no longer guarantee that all Yellowfin features will be available should you choose to continue to use IE11. Users who access Yellowfin via IE11 might be presented with a splash screen when Yellowfin starts up, warning users that the browser is out of date and no longer supported. Users can click on the Continue button to access Yellowfin, but full functionality will not be available. Users can view existing content and create new Reports. To create or edit an existing dashboard, presentation or story, please upgrade to a modern, supported browser.
Server Requirements Concurrent UsersThe 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. Recommended minimum specifications based on the number of concurrent users and minimum background task usage:
Note: The table above shows single server requirements. Yellowfin can be deployed as a cluster to spread the workload across multiple smaller servers. For example, 150 users could be handled by 4 Quad Core servers in a cluster, rather than a single 16 core machine. |
...