Ocient System Sizing

the {{ocient}} system must be the proper size for your data and query requirements follow these steps to determine the size of your ocient system contact https //ocient com/contact sales/ to aid with the ocient system calculations, established configuration, and node quantities gather the uncompressed size of your current database or data and its format if your data resides in a database, determine the compression ratio of the data further, consider whether your data is streaming or file based for streaming or time series data, investigate the level of data granularity (for example, minute, hour, or day) calculate the quantity of data (in gbps or the number of rows in a specific unit of time) that you plan to load into the ocient system and at what cadence (for example, continuous loading or specific schedule) describe the latency you expect between the data creation and when data reaches the destination as you consider the quantity, determine the percent of null data also, think about the retention period required for the data determine the level (small, medium, or large) of data transformation in the data pipeline loading process see whether you require any user defined transformations investigate whether your transformations are done programmatically or using sql after the initial data load, see if you require more transformations, such as cubes or views investigate the types of queries you plan to execute (for example, simple filters, complex aggregation or sorting, complex joins, or transformation) in addition, review your query workload (number of queries in a specific unit of time) and how many queries you expect to execute in parallel consider any objectives you have for system readiness to execute queries calculate the compressed data volume consider your compression requirements for the stored data (for example, global dictionary compression) add index, statistics, working space, and parity size to the compressed data volume use the established storage space configuration in the ocient system for data nodes, parity nodes, and the number of clusters using the known size and level of transformation in loading, determine the total number of cores, memory, and storage for your requirements calculate the number of sql nodes, loader nodes, foundation nodes, metadata nodes, and supporting nodes ocient personnel assist with this step the number of specific nodes determines the size of the ocient system after you have the latter numbers, then you can purchase, install, and configure the system related links docid\ jopccanxfdrocwkl0qcfv docid\ wmnkngun5beeuhcmk73bj docid gac3iwnrtwwnndngn50b docid\ gbrio6u37loupxxusodyb docid\ ssxi4zc3p mqdtr0b7qdn