Today, Vertica is announcing its 3.5 release, timed in line with a TDWI conference. Vertica 3.5 is scheduled to go into beta test in mid-August and be released to general availability in early October. Vertica 3.5 highlights include:
- Vertica/MapReduce integration, which I’m covering in a separate post.
- A new storage architecture called Vertica FlexStore, which seems to boil down essentially to three things:
- A sort of row/column hybridization — Vertica would probably prefer to call it something like a column clustering feature — that I’m also covering in a separate post.
- The beginnings of a multi-temperature capability, somewhat akin to Teradata Virtual Storage.
- Enhancements to Vertica’s WOS (Write-Optimized Store, the in-memory part of Vertica that first receives updates). I don’t understand WOS architecture well enough to write about that yet.
- Load-balancing, to route queries evenly among Vertica nodes — probably just round-robin — rather than having them just be processed by whichever node happens to receive them.
And Vertica 3.5 surely includes some lesser features as well.
Like Teradata Virtual Storage, Vertica FlexStore wants to partition data among different parts of storage automatically. But, unlike Teradata’s technology, it will grudgingly let you do it by hand if you insist. Since Vertica installations seem to generally have only one kind of disk each — and that kind spinning rather than solid-state — early tests concentrate on allocating data among the inner and outer tracks of a disk. Vertica said that one typically gets 80% of the benefit by dividing the data into just two partitions, and 90% of the benefit if one divides it into three. However, I don’t recall getting a clear estimate of just how large that benefit is.