Hyper-threading is ignored for the purposes of counting cores. Physical cores can represent actual server hardware or cores on a virtual machine (VM). To obtain the exact size of the repository data, open the backup file and use the size of the workgroup.pg_dump file.Ĭore count is based on "physical" cores.To obtain an estimate of the repository data, check the size of /pgsql/data/base directory. The temp directory, which is where an extract is stored to during a refresh, may require up to three times the final file size of the extract. You can use this amount of disk space to help you figure out how many extracts will be published to Tableau Server over time as well as how each existing extract will increase in size.Ĭonsider the space needed by the temp directory during an extract refresh. Test your needs by publishing several extracts to Tableau Server, and then checking the disk space used. Consider the number of extracts that will be published to Tableau Server and the size of each extract.In addition, you must also take into account the repository backup size unless you specifically choose the option to do your repository backup separately as described in the Option 2: Back up repository separately topic. Network attached storage space requirements for External File Store: If you are planning to configure Tableau Server with External File Store, you will need to estimate the amount of storage space to dedicate on your network attached storage.Įstimating the storage size: You must take into account the amount of storage needed for publishing and refreshing extracts. You may need to allocate additional disk space depending on various factors like whether you will be using extracts. The Setup program uses about 1 GB of space. Important: The disk space requirement cannot be checked until you initialize TSM.įree disk space is calculated after the Tableau Server Setup program is unzipped. Nodes must meet or exceed the minimum hardware recommendations, except:ĭedicated Backgrounder nodes running up to two instances of backgrounder, where 4 cores may be acceptable.ĭedicated node for Tableau Prep Conductor: Minimum of 4 cores (8 vCPUs), and 16 GB of RAM.ĭedicated node for Independent Gateway: Minimum of 2 cores (4 vCPUs), 8 GB of RAM, and 100 GB free disk space. This node should have a minimum of 4 cores (8 vCPUs), and 16 GB of RAM. If you are adding Tableau Prep Conductor to your Tableau Server installation, we recommend you add a second node and dedicate this to running Tableau Server Prep Conductor. Must support SSE4.2 and POPCNT instruction sets.The following list describes the minimum hardware recommendations for a production use, single- node installation of Tableau Server: ![]() Hardware recommendations for production installations Moving forward, we are committed to investing in the EDG reference architecture to ease feature rollouts and improve upgrade scenarios. The EDG presents a fully-tested and supported, performant, scalable, secure reference architecture based on a tiered data network. ![]() ![]() If you have determined that you must self-host Tableau Server, we recommend following the prescribed Tableau deployment in the Enterprise Deployment Guide (Link opens in a new window) (EDG). For information about the viability of Tableau Cloud for your organization, review this blog post, Should I move my analytics to the cloud? (Link opens in a new window)Īlready running Tableau Server and want to migrate to Tableau Cloud? See Tableau Cloud Manual Migration Guide (Link opens in a new window). For most organizations, Tableau Cloud will provide a more reliable, performant, and cost-effective analytics solution when compared to self-hosting Tableau Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |