Capture digital ad events and track performance metrics in realtime.

View the Project on GitHub VoltDB/app-adperformance

VoltDB Example App: Ad Performance

Use Case

This application simulates a high velocity stream of events (impressions, clickthroughs, conversions) that are enriched and ingested. These events are randomly generated in the client, but represent a stream of events that would be received from web traffic.

The "TrackEvent" stored procedure processes these events. It looks up the corresponding advertiser and campaign based on the creative ID which represents which ad was shown. It also retrieves the corresponding web site and page based on the inventory ID from the event. The timestamp and event type fields are converted to aid in aggregation, and all of this data is then inserted into the impression_data table.

Several views maintain real-time aggregations on this table to provide a minutely summary for each advertiser, plus drill-down reports grouped by campaign and creative to show detail-level metrics, costs and rates with real-time accuracy.

Several new SQL features in VoltDB are demonstrated in this application, including:

Code organization

The code is divided into two projects:

See below for instructions on running these applications. For any questions, please contact


Before running these scripts you need to have VoltDB 4.0 (Enterprise or Community) or later installed, and you should add the voltdb-$(VERSION)/bin directory to your PATH environment variable, for example:

export PATH="$PATH:$HOME/voltdb-ent-4.0.2/bin"


  1. Start the database in the background


  2. Run the client application


  3. Open the web/adperformance.html page in a web browser to view the real-time dashboard

  4. To stop the database and clean up temp files

    voltadmin shutdown ./


You can control various characteristics of the demo by modifying the parameters passed into the InvestmentBenchmark java application in the script.

Speed & Duration:

--duration=120                (benchmark duration in seconds)
--autotune=true               (true = ignore rate limit, run at max throughput until latency is impacted)
                              (false = run at the specified rate limit)
--ratelimit=20000             (when autotune=false, run up to this rate of requests/second)

Metadata volumes and ratios:

--sites=100                   (number of web sites where ad events may occur)
--pagespersite=10             (number of pages per web site)
--advertisers=100             (number of advertisers)
--campaignsperadvertiser=10   (number of campaigns per advertiser)
--creativespercampaign=5      (number of creatives or banners per campaign)

Instructions for running on a cluster

Before running this demo on a cluster, make the following changes:

  1. On each server, edit the file to set the HOST variable to the name of the first server in the cluster:


  2. On each server, edit db/deployment.xml to change hostcount from 1 to the number of servers:

  3. On each server, run the start script:


  4. On one server, Edit the script to set the SERVERS variable to a comma-separated list of the servers in the cluster


  5. Run the client script: