Top
VoltDB v8.1 Released - VoltDB
12840
post-template-default,single,single-post,postid-12840,single-format-standard,mkd-core-1.0,highrise-ver-1.0,,mkd-smooth-page-transitions,mkd-ajax,mkd-grid-1300,mkd-blog-installed,mkd-header-standard,mkd-sticky-header-on-scroll-up,mkd-default-mobile-header,mkd-sticky-up-mobile-header,mkd-dropdown-slide-from-bottom,mkd-dark-header,mkd-header-style-on-scroll,mkd-full-width-wide-menu,mkd-header-standard-in-grid-shadow-disable,mkd-search-dropdown,wpb-js-composer js-comp-ver-6.0.5,vc_responsive
VoltDB / Announcements  / VoltDB v8.1 Released

Blog

VoltDB v8.1 Released

We are pleased to announce VoltDB v8.1. This release includes features that can reduce the total cost of ownership of your VoltDB solution, with improvements to memory management of replicated tables, and performance improvements for many applications. These features include:

  • Reduced Memory for Replicated Tables
    Replicated (i.e. non-partitioned) tables are now stored only once per cluster node, rather than being stored once per partition. For replicated tables with a large number of rows or on clusters with large sites-per-host, this can save a significant amount of memory and reduce the total cost of ownership for your VoltDB cluster.
  • Faster Bulk-loading of Replicated Tables
    If you’re using one of VoltDB’s loaders, such as csvloader or jdbloader, or have written your own loader using the BulkLoader API, you may notice up to a 3x speedup for loading replicated tables.
  • Improved Ad Hoc Read Query Performance on Replicated Tables — Ad hoc queries that perform read-only operations on replicated tables have traditionally been executed by a single partition within the database, assuming such queries are a small percentage of the overall workload. V8.1 changes the execution model to “round robin” read-only queries of replicated tables to more evenly distribute the workload.
  • Performance Optimization of “Paging” Queries
    Previously, using SQL LIMIT/OFFSET to get to a range of values would have to scan the table to determine the starting point, causing each successive “page” to take longer to get to. With this optimization, LIMIT/OFFSET queries can take advantage of an index on the table to directly access the data.

For a full list of v8.1 features and fixes, visit our Release Notes. If you have questions or feedback, drop a note to support@voltdb.comDownload VoltDB v8.1 and give it a try.

Post Tags: