Vertica分布式数据库

Item	Limit
Number of nodes	Maximum 128 (without Vertica assistance).
Database size	Approximates the number of files times the file size on a platform, depending on the maximum disk configuration.
Table size	2^64 rows per node, or 2^63 bytes per column, whichever is smaller.
Row size	32 MB. The row size is approximately the sum of its maximum column sizes, where, for example, a VARCHAR(80) has a maximum size of 80 bytes.
Key size	Limited only by row size
Number of tables/projections per database	Limited by physical RAM, as the catalog must fit in memory.
Number of concurrent connections per node	Default of 50, limited by physical RAM (or threads per process), typically 1024.
Number of concurrent connections per cluster	Limited by physical RAM of a single node (or threads per process), typically 1024.
Number of columns per table	1600.
Number of rows per load	2^63.
Number of partitions	1024. While Vertica supports a maximum of 1024 partitions, few, if any, organizations will need to approach that maximum. Fewer partitions are likely to meet your business needs, while also ensuring maximum performance. Many customers, for example, partition their data by month, bringing their partition count to 12. Vertica recommends you keep the number of partitions between 10 and 20 to achieve excellent performance.
Length for a fixed-length column	65000 bytes.
Length for a variable-length column	65000 bytes.
Length of basic names	128 bytes. Basic names include table names, column names, etc.
Query length	No limit.
Depth of nesting subqueries	Unlimited in FROM, WHERE, or HAVING clause.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/11420681/viewspace-767413/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/11420681/viewspace-767413/