One challenge we have at NuoDB is giving people a “hands on” understanding of what we do, in a quick and efficient way. We recently set the goal of creating a technical guided tour that showed off some of NuoDB's value propositions in a way that was simple, quick, and could work on a single laptop. Given that NuoDB is a distributed database, that last requirement made things a bit tricky! We wanted to give the user an introduction and provide familiarity with NuoDB concepts and tools, to generate a Wow!
Every release, NuoDB gets easier to use, and release 2.3 has added a preview feature that promises to make the life of a systems administrator much easier: hot copy. (The use of preview features is encouraged in development projects but not yet suppored in deployments.)
Hot copy uses one of the existing Storage Managers (SM) or Snapshot Storage Managers (SSM) to create a transactionally consistent copy of the archive and journal of a database with no interruption of service. The database continues running and transactions keep processing, even in a single host database.
Throughout the development of our new Robins release (NuoDB 2.3), we’ve been benchmarking performance against our previous Larks release (NuoDB 2.2). We wanted to demonstrate the improvements to scale-out performance that we’ve been working on for Robins.
To do this we needed a realistic, or at least pseudo-realistic, test of transaction processing to make the benchmarking worthwhile. So we used DBT2 as a credible, public domain scenario (the detail of DBT2 is at the end of this post) and configured it to increase the number of warehouses as the number of clients increased.