Page History
...
Expand | ||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||
Yellowfin Stories are relatively lightweight but requires resources to account for concurrent users reading a story. Stories have embedded Yellowfin reports, therefore the recommended specification will be the same as the Data Discovery product. Functional Application Server RequirementsYellowfin requires a minimum specification to be functional. The Yellowfin service will start on the following server specification:
Note: This specification is only recommended for roughly 30 concurrent users who are reading or creating Stories which do not have reports. 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 for up to roughly 100 concurrent story consumers.
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.
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 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.
|
Anchor | ||||
---|---|---|---|---|
|
...