Welcome Guest | My Membership | Login

MultiValue Database and Framework Benchmarking


Benchmarking has been a topic that's been floated around for several years, but the MultiValue Community doesn't have much in the way of prepackaged tools. I've heard many different reasons for the lack of standard benchmarking tools, so I'll go through a few of them.

What are TPC.org Benchmarks?

There are many benchmarks out there for a wide variety of other environments, but I'm going to focus on the most popular. For many years, the TPC.org benchmarks have been what most people think of when talking about Benchmarking. You've probably heard of the TPC-C, TPC-H, and TPC-E versions. These have become the industry standards as benchmarks that people want to use. But, like any benchmark tool, they all have drawbacks as well.

The TPC-C benchmark is the most common, mainly due to how old it is. TPC-C has been around since 1992. It is designed to model an OnLine Transaction Process (OLTP) wholesale application. Since it was designed over twenty years ago, it made some assumptions about the hardware that don't hold up today. Mostly, it expected that machines did not a have a lot of RAM and it expected inefficient Disk IO. The TPC-E benchmark was created as a more modern replacement for the aging TPC-C benchmark. TPC-E uses an OLTP stock exchange as its data model. The design is more sophisticated in its simulation of a real-world system. It takes into account the fact that modern servers use lots of RAM and other system resources to offset the slower Disk IO.


Social Media Login

Use your existing social media logins to access your Membership/Subscription information.

Existing Magazine/Newsletter Subscriber (Quick Access)

If you are an existing International Spectrum subscriber, but have not registered with the website, please enter the Reference Code found on the magazine or in the e-mails you receive from us.

Magazine Reference Code location

Spectrum Login

New Subscriber

If you currently do not receive the Magazine or other emails from International Spectrum, select the "Subscribe" button below to create an new membership account.


Find out more about the different between the FREE and a Professional Membership at:
Compare Account Options


# # #          # # #          # # #


Related Articles

  • From the Inside July/August 2017

    We're already planning for the next Spectrum conference. If you haven't yet seen the information for the 2018 Spectrum, it will be April 23rd-26th at The Henderson in Destin, Florida. This is a new venue for the conference.

  • The Six Million Dollar Open

    Company: International Spectrum

    The term extensible means that a language or format can be tweaked, adjusted, or expanded by the users. It can go beyond what the original designers had in mind. MvBASIC is extensible. The open command is an excellent candidate for an extensible makeover.

  • Expanding Your Toolkit: JSON vs. XML

    MultiValue strings are an excellent way to express data compactly. In a world where, increasingly, every system seems to need to talk to every other system, it is useful — and desirable — to have as many communication formats available to you as is reasonable. Last time out, Bennett Barouch gave you a good look at JSON. This time he's pulling back the curtain on XML.

  • Call(Overhead)

    For decades, MV BASIC has featured the CALL() statement, allowing for external subroutines invoked by mainline programs. Typically, one does this to share common code/ processing/algorithms, thus upholding the development principle of DRY (Don't Repeat Yourself). However, such features often come with a performance penalty. How much of a performance penalty?

  • Improving System Performance BASIC Efficiency

    Database: Advanced Pick, D3, jBASE, Mentor/PRO, mv*Base, mvEnterpise, OpenQM, PI/Open, PRIME, R83, Reality, Ultimate, UniData, UniVerse, UniVision, OpenInsight, MVON, AREV

    The task was designed to transfer geological survey data to tape for distribution. This data was kept in separate files according to type. These types included seismic section, well log, and well core data. The process was taking over 72 hours.

Return to top